swarm_init

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

Annotations provide readOnlyHint=false and destructiveHint=false, but the description adds minimal behavioral context. It does not disclose side effects (e.g., changing engine mode, potential conflict if a swarm already exists) or requirements like network configuration.

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 front-loaded with the purpose statement, followed by a clear list of parameters. It is moderately concise without unnecessary words, though the list could be more integrated into prose.

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?

The description covers the return value (node id) and parameter meanings, but lacks context on prerequisites, error conditions, or interactions with other swarm operations. Given the tool's complexity (11 params, output schema), it is adequate but not comprehensive.

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?

The description provides one-line explanations for each of the 11 parameters (e.g., 'Externally reachable address advertised to other nodes'), adding meaning beyond the schema which only has types and defaults. Since schema coverage is 0%, this is valuable, though more detailed constraints or validation would improve it.

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 'Initialize a new swarm on this Engine' with a specific verb and resource. It distinguishes from sibling tools like swarm_join (join existing) and swarm_inspect (inspect), making the purpose unambiguous.

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?

No guidance on when to use this tool versus alternatives. It does not explain prerequisites (e.g., engine not already in a swarm) or when one might prefer this over swarm_join or swarm_update.

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