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

With no annotations, the description does real work: it discloses that rationale is mandatory and that it is published on the manager's log, an externally visible side effect an agent wouldn't otherwise know. It omits whether deletion is reversible, what happens to bots assigned to that formation, and any permission requirements.

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?

Two short sentences, no waste, with the scoping constraint front-loaded and the critical REQUIRED constraint on rationale given next. Every clause earns its place.

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?

Output schema exists, so return values needn't be described. But for a destructive tool with zero annotations, the description should state reversibility and side effects on dependent entities; it covers only the rationale requirement and the log publication.

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 0% — fund_id and formation_id carry only titles in the schema, and the description adds nothing about them. It does fully explain the rationale parameter (required, its purpose, and its published destination), which partially compensates but leaves two identifiers undocumented.

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?

States a specific verb (delete) and resource (formation) plus a scoping qualifier, 'from the bench (not the one on the field)', which separates it from switch_formation and update_formation without naming them. An agent can identify the operation, though the sibling names themselves aren't cited.

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 parenthetical 'not the one on the field' implies a when-not condition (don't delete the active formation), but it stops short of naming the alternative action (switch_formation first, then delete) or stating prerequisites.

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