boss_preset_list

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the role/platform availability constraints, which is real context an agent cannot get from the empty schema, but it says nothing about ordering, result shape, or whether the list is empty when no presets exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded clause states the action, followed by a compact bracketed availability gate. No redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only listing tool with no output schema, the description covers what is listed and who may call it. Only minor gaps remain, such as what fields a preset entry contains or what an empty result means.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema baseline of 4 applies. There is no parameter meaning for the description to add or omit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

"列出所有搜索预设" states a specific verb (list) and resource (search presets), which cleanly separates it from the sibling mutation tools boss_preset_add and boss_preset_remove. It does not explicitly name those siblings, but the read-only listing framing makes the distinction obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The bracketed availability clause (roles=candidate; candidate_platforms=zhipin; recruiter_platforms=-) tells the agent when the tool is callable, which is genuinely useful gating information. However, it gives no guidance on when to list presets versus using boss_preset_add/remove or how the results relate to boss_search, so usage is only partially implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.