report_host_wave

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

No annotations provided, so description carries full burden. It mentions reporting completion and setting terminal, but does not disclose whether the tool mutates state, requires permissions, or has side effects. Adequate but not fully transparent.

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?

Three sentences, zero wasted words. Front-loaded with purpose and essential usage instructions. Exemplary conciseness.

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 annotations or output schema, the description covers the main purpose, when to call, and key parameter usage. Slight gap in not mentioning return value or error scenarios, but overall sufficiently complete for a reporting tool.

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 description coverage is 50% (5 of 10 params have descriptions). The description adds meaning to workspace_root and output_excerpt beyond schema, but many params (wave, agents, outcome, terminal) lack additional semantic context. Compensates partially but not fully.

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?

Description clearly states verb 'report completion' and resource 'one host-native swarm/plan wave', distinguishing it from sibling 'report_host_swarm_complete' which likely reports entire swarm completion. It also provides specific actions like passing workspace_root and setting terminal.

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?

Description gives explicit guidance: 'Call after spawning and finishing each host_spawn_waves wave', and instructs to set terminal=true on last wave with outcome enum. While it doesn't explicitly state when not to use, the positive guidance is clear and sufficient.

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