internal_squad_delete_internal_squad

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

No annotations are provided, so the description carries the full behavioral burden. For a destructive DELETE it discloses nothing about irreversibility, whether associated users are cascaded or orphaned, required permissions, or side effects; only the raw HTTP method is exposed, which the agent could already infer.

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 text is short and front-loads the endpoint, but the 'Tags: Internal Squads Controller' line is scaffolding noise that adds nothing for an agent. It is compact without being informative.

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, no-annotation tool with no output schema, the description omits critical context, notably that without confirm:true the call only returns a preview and is not sent. That safety-critical behavior lives only in the schema's Russian-language parameter description, leaving the tool definition thin.

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 description coverage is 50%: uuid has no prose but is self-documenting via format/pattern, while confirm carries a detailed in-schema description of the preview-vs-execute behavior. The description only surfaces {uuid} in the path placeholder and adds no meaning beyond the schema, failing to compensate for the coverage gap.

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 states a specific verb (Delete) and resource (internal squad) and exposes the exact endpoint DELETE /api/internal-squads/{uuid}, so an agent knows it removes an existing squad by UUID. It is essentially the tool name restated and offers no explicit contrast with siblings like internal_squad_update_internal_squad, but the verb+resource pairing is 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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as internal_squad_remove_users_from_internal_squad or external_squad_delete_external_squad. The agent must infer the usage context entirely from the name.

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