boss_preset_list

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

The description includes availability constraints (roles=candidate, candidate_platforms=zhilian, zhipin, recruiter_platforms=-), which informs the agent about the tool's applicable contexts. Since no annotations are provided, this adds valuable behavioral context.

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?

The description is a single line and front-loads the main purpose. However, it has a slight redundancy with repeated '可用性:' but overall efficient.

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 simple listing tool with no parameters and no output schema, the description provides the core purpose and availability. It does not mention return format, but given the tool's simplicity, this is mostly sufficient.

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 input schema has 0 parameters, so there is no parameter documentation needed. The baseline for 0 params is 4, and the description does not mislead about parameters.

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?

The description clearly states '列出所有搜索预设' (list all search presets), which is a specific verb+resource. It distinguishes from sibling tools like boss_preset_add and boss_preset_remove, which involve adding or removing presets.

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 description does not provide any guidance on when to use this tool versus alternatives. It only includes availability info but no explicit when-to-use or when-not-to-use context.

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