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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), so the bar is lower, and the description goes well beyond them by disclosing the signing requirement (X-Agent-Id/X-Signature/X-Timestamp), dual-transport behavior, and single-use signatures on the SSE bridge. It does not explain what 'opt out' actually removes or destroys, which is the one notable gap against destructiveHint=true.

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?

Purpose is front-loaded in the first sentence, followed by the operationally essential auth and transport notes. The transport sentence is dense and specific to the legacy SSE bridge, but it is genuinely actionable rather than filler, so the length is justified.

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 mutating, signed, multi-transport tool with no output schema, the description covers side effects, auth, and transport adequately. It partially covers returns (the connect_now recipe) but never describes the shape of the status-check response, which is the remaining omission.

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%, so baseline is 3, but the description adds real meaning for enable:true (pushes standing orders to the inbox and returns the connect_now recipe) and ties agent_id to the X-Agent-Id signing header. This is more than the schema's terse 'true to opt in, false to opt out'.

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 states a concrete action set (opt in/out of swarm participation, check coordinator status, get a harness command recipe) with the resource being swarm membership. However, the name 'enable_swarm' only captures one of three behaviors, and the multi-purpose scope is not reconciled with the title, so an agent must read the whole sentence to know it is also a status/recipe tool.

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?

It gives a conditional for the enable parameter ('Calling with enable:true pushes standing orders...') and notes that omitting it yields a status check, which is implicit usage guidance. But it names no alternatives among the large sibling set (e.g. ack_standing_orders, agent_heartbeat, register_agent) and states no when-not-to-use conditions.

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