boss_clean

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

No annotations are provided. The description implies a destructive action (cleaning/deleting). The schema parameters 'dry_run' and 'all' add some behavioral info, but the description itself does not disclose what exactly is deleted, whether it's safe, or any side effects. It is adequate but not thorough.

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 short but includes a messy and repetitive availability block ('可用性: 可用性:'). The core purpose is front-loaded, but the availability info could be more concise and structured.

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?

Given no output schema, no annotations, and a simple parameter set, the description covers the basic purpose. However, it lacks details on when to use the tool (e.g., maintenance tasks, performance issues) and behavioral expectations, leaving gaps for an agent unfamiliar with the domain.

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?

Schema coverage is 100% with clear descriptions for both parameters ('dry_run: only preview, all: full cleanup'). The tool description does not add further semantic value beyond the schema, which is acceptable given the schema already fully documents the 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 the tool's purpose: '清理过期缓存和临时文件' (clean expired cache and temporary files). This is a specific verb and resource combination that distinguishes it from all sibling tools, which focus on AI analysis, search, job management, etc.

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 provides availability constraints (roles and platforms) but does not offer guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The availability info is somewhat repetitive and unclear.

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