Api teams destroy

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

The annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is fully covered by structured data. The description adds nothing on top of that — no mention of cascade effects, permission requirements, or irreversibility beyond what the hints state.

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?

Extremely short, but this is under-specification rather than conciseness: the single token carries no information beyond the tool name and has no front-loaded explanation of action or scope.

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, open-world delete operation with no output schema and an undocumented parameter, the description should at minimum state what gets removed and what is required. It supplies none of that, leaving the agent entirely dependent on annotations and the name.

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 0% for the single required 'id' parameter, and the description does not compensate at all — it never says whether the id is a UUID, slug, or numeric key. The parameter is simple enough to be inferable from its name, but the description contributes no semantic value.

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 is only the raw operation identifier "api_teams_destroy", which merely restates the tool name and title. An agent can infer deletion of a 'team' entity, but nothing distinguishes it from siblings like ciso_assistant_api_teams_partial_update or ciso_assistant_api_teams_batch_action_create beyond the word 'destroy'.

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 guidance whatsoever about when to use this tool, when not to, or which alternatives (e.g. teams_partial_update, teams_batch_action_create) apply. The description provides zero routing information.

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