delete_team

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely useful behavioral context beyond them: this is a soft delete that moves the team to trash and can be restored. That 'reversible delete' detail is exactly what an agent needs and is not captured by the annotations.

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?

Front-loaded and short, but the first two sentences restate each other ('Delete a team.' / 'Delete a team using its unique identifier.'), wasting a sentence on redundancy rather than adding information.

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 with no output schema, the reveal that deletion is soft and reversible is important and present. However, the unaddressed `with` parameter and the absence of any side-effect or permission detail leave the definition only minimally complete.

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 reported at 0% despite 2 parameters. The description hints at 'its unique identifier' (mapping loosely to teamId) but says nothing about the `with` relation-inclusion parameter, so it does not compensate for the schema's gaps.

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+resource ('Delete a team') and clarifies it operates on a unique identifier. It does not differentiate from close siblings like post_batch_delete_teams or delete_team_member, but the core purpose 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?

No guidance on when to use this versus restore_team, post_batch_delete_teams (batch alternative), or delete_team_member. The description only notes that deletion is reversible, without routing the agent to related tools or stating prerequisites.

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