01Safety
30.0 / 30
What changed in the harness
Selection accuracy 100→100, token cost up 4%, unconfirmed writes 100%→100%.
Category breakdown
Where the score comes from.
Earned points across the four signals Gradable measures. Safety and Legibility are scored out of 30; Economics and Discoverability are scored out of 20.
02Legibility
28.8 / 30
03Economics
20.0 / 20
04Discoverability
19.7 / 20
Highest-impact fix
Estimated gain +1 pointRewrite 3 underspecified tool descriptions
State each tool's behavior, explain every parameter, and declare return semantics, prioritizing tools exercised by failed selection tasks.
Description evidence
Defects and rewrites.
3 defects found across the exposed tool descriptions. Suggested rewrites make purpose, inputs, boundaries, and returns easier for an agent to understand.
| Tool | Defect types | Suggested rewrite |
|---|---|---|
getBaziDetail |
no_return_description |
根据时间（公历或农历）、性别来获取八字信息。solarDatetime和lunarDatetime必须传且只传其中一个。返回四柱干支（年柱、月柱、日柱、时柱）及其对应的五行、十神等命理详情。 |
getSolarTimes |
no_return_description |
根据八字获取匹配的公历时间列表。返回符合该八字的所有可能公历日期时间组成的数组，格式为：YYYY-MM-DD hh:mm:ss。 |
getChineseCalendar |
no_return_description |
获取指定公历时间（默认今天）的黄历信息。返回当日的农历日期、宜忌事项、生肖、节气等传统黄历信息。 |
Selection evidence
Confusable tool pairs.
3 pairs where similar names or overlapping descriptions may send an agent toward the wrong tool.
| Tool A | Tool B | Confidence | Why they collide |
|---|---|---|---|
getBaziDetail |
getSolarTimes |
medium | Both convert between BaZi (八字) and calendar time, just in opposite directions; a task like '根据八字算出对应的公历时间/生日' could lead an agent to call getBaziDetail (which requires gender/birth time to produce BaZi) instead of getSolarTimes (which takes a BaZi string and returns matching solar dates), since both deal with 'bazi + time' conceptually. |
getSolarTimes |
getChineseCalendar |
low | Both return calendar/solar time information, but their inputs differ sharply (BaZi string vs. optional solar datetime) and purposes are distinct enough (reverse-lookup birth times vs. daily almanac info) that confusion is unlikely except in vague prompts about '查询农历/公历日期信息'. |
getBaziDetail |
getChineseCalendar |
low | Both accept a solarDatetime parameter and relate to Chinese calendar concepts, so a vague request like '查一下这个日期的信息' could ambiguously route to either, but their outputs (personal BaZi chart vs. general almanac/黄历 info) are conceptually distinct enough to keep confusion low. |
Compare the field