squads_delete

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a dangerous write. The description adds no further behavioral context such as whether the delete is permanent, what happens to users in the squad, or if confirmation is needed. It merely restates the name.

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?

At three words, the description is extremely concise but under-specified to the point of being unhelpful for invocation. It is front-loaded but does not earn its place by adding any practical guidance.

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 delete tool with no output schema, the description should explain the impact of deletion (e.g., removal of squad and associations) and any important caveats. It provides none of this, leaving the agent to infer behavior from the annotations alone.

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 schema provides a required uuid with format 'uuid' but no description. The tool description does not mention or explain the parameter at all, so it fails to compensate for the 0% schema description coverage. Only the parameter name and format give any hint.

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 uses a specific verb ('Delete') and resource ('internal squad'), and the word 'internal' distinguishes it from the sibling external_squads_delete. However, it does not fully differentiate from other squad operations like squads_get or squads_update beyond the verb.

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?

There is no indication of when to use this tool versus alternatives (e.g., external_squads_delete), no prerequisites, and no mention of side effects or required permissions. It only implies that deletion is the action.

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