Broadcast an advert

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

Annotations indicate non-read-only, non-destructive, non-idempotent behavior. The description adds value by noting 'Costs airtime; flood propagates mesh-wide', which are key behavioral traits not captured by annotations. However, it does not detail all edge cases (e.g., behavior on invalid nodes).

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 three sentences, front-loaded with the core purpose and mode selection. Every sentence adds value: purpose, node usage, cost/propagation. No wasted words, clearly 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 the tool's moderate complexity (3 parameters, no required fields, enum, output schema exists), the description covers the essential behavioral aspects (mode, node targets, cost). It lacks explanation of dryRun output or error handling, but the output schema likely fills gaps.

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 100%, so baseline is 3. The description reinforces the meaning of 'mode' and 'node' (e.g., 'omit to target home') but does not add significant extra semantic detail beyond what the schema provides for all parameters, especially 'dryRun'.

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 action ('Send an advert') and the resource ('from a node'). It distinguishes between flood and zerohop modes and gives a specific equivalent to the admin command, helping the agent understand its purpose among sibling tools.

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 explains when to use each mode ('flood' vs 'zerohop') and how to target the home node by omitting the 'node' parameter. It warns about airtime costs and mesh-wide propagation, but does not explicitly exclude alternative tools or provide when-not-to-use guidance.

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