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

Beyond the destructiveHint annotation, the description discloses it's a soft-delete, recoverable for 7 days, and requires confirm: true. This gives critical behavioral context the annotation alone lacks.

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?

Single, front-loaded sentence with all necessary information; no wasted words.

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 destructive action, the description covers the action, recovery window, and confirmation requirement. Output schema exists so return values need not be described; slight gap on what 'preview' entails but acceptable.

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 explains the 'confirm' parameter ('true to apply') but does not describe 'tournament_key', relying on the parameter name. Since schema description coverage is 0%, the description partially compensates but could be more explicit.

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 ('Soft-delete the whole tournament') with a specific verb and resource, and distinguishes from sibling tools like end_tournament or remove_player by indicating the scope ('whole tournament'). The recovery note also clarifies the nature of the delete.

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?

Provides explicit usage guidance: 'Preview first; confirm: true to apply.' This tells the agent the prerequisite and required confirmation. However, it does not explicitly name alternative tools or exclusions, so not a 5.

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