external_squad_delete_external_squad

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

No annotations are provided, so the description carries full burden. It states the HTTP method and route (which implies destructive mutation) but doesn't disclose what is destroyed, whether deletion is reversible, cascade effects on squad members, or permission requirements. The confirm gating appears only in the schema, not the description.

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?

Very short but wastes lines on redundant metadata: 'Delete external squad' restates the tool name, and 'Tags: External Squads Controller' is HTTP client boilerplate rather than useful agent-facing context. The route line is the only genuinely informative part.

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 deletion tool with no annotations and no output schema, the description is inadequate: no confirmation of irreversible effects, no cascade/member implications, no error or not-found behavior. The schema's confirm field hints at a safety flow but the description never explains it.

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% – both the uuid and confirm parameters have descriptions in the schema, including the important confirm-preview behavior. The description adds no parameter meaning beyond what the schema already provides, so baseline 3 applies.

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 (external squad) plus the exact route DELETE /api/external-squads/{uuid}. Siblings like external_squad_get_external_squads and external_squad_update_external_squad are implicitly distinguished by the verb, though the description doesn't explicitly contrast them.

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 when-to-use guidance, prerequisites, or alternatives named. The confirm parameter implies a preview-then-confirm flow, but the tool description itself doesn't explain when to call this versus related tools like external_squad_remove_users_from_external_squad.

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