delete_team

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

With no annotations, the description carries the full burden. It usefully discloses that deletion cascades to memberships and scope grants, which is real behavioral context beyond the name. However, it omits irreversibility, required permissions, and what happens to artifacts owned by the team, and pads the rest with marketing copy.

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 purpose is correctly front-loaded in the first sentence, but three of the four sentences are plan/upgrade marketing that does not help an agent select or invoke the tool, so a large share of the text does not earn 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?

For a destructive, cascading delete with no annotations and no output schema, the description should explain permissions, irreversibility, and consequences. It offers only a garbled plan requirement plus promotional content, leaving the operationally important behavior undocumented.

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% and the single required parameter team_id has no schema description. The description never explains the parameter's format, source, or how to obtain it, so it does not 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 first sentence gives a specific verb and resource ('Delete a team') and adds the cascade scope ('its memberships, and its scope grants'), which meaningfully distinguishes it from sibling mutations like remove_team_member or delete_design. It stops short of naming a sibling it is not, so it is clear but not fully differentiated.

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 guidance: nothing tells the agent when to delete a whole team versus removing individual members via remove_team_member, or what prerequisites precede deletion. The plan/upgrade sentences are about pricing, not invocation conditions, so they provide no actionable selection guidance.

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