boss_batch_greet

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

With no annotations, the description bears full burden. It discloses the maximum of 10 greetings ('上限 10') and implies a search-then-greet sequence. The presence of a 'dry_run' parameter in the schema adds transparency, but the description does not elaborate on side effects or write behavior.

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 concise phrase, efficiently conveying core purpose. It could be slightly more structured but is not verbose.

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 the tool's complexity (search + batch greet) and lack of output schema, the description is minimal. It does not explain the process (e.g., how greetings are sent), the role of 'dry_run', or return values, leaving gaps in understanding.

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 each parameter described. The description adds '上限 10' which reinforces the limit parameter but does not add significant meaning beyond the schema's '最大打招呼数量' description.

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 '搜索后批量打招呼（上限 10）' clearly states it performs a batch greet after searching with a limit of 10. It uses a specific verb-resource combination ('batch greet') and distinguishes from sibling tools like 'boss_greet' (single greet) and 'boss_search' (just search).

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 implies usage after a search ('搜索后') but does not explicitly state when not to use this tool or provide alternatives. No mention of prerequisites or exclusions.

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