Contract Testing: Admin Delete Team

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

The description only restates the destructive nature ('Delete') which annotations already cover with destructiveHint=true and idempotentHint=true. No additional context on irreversibility, cascading effects, or preconditions. The description adds minimal value beyond 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?

The description is short and front-loaded with the purpose. However, the 'Toolset: Admin' line is redundant given the title and name, making it slightly less concise. Still efficient overall.

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 simple delete tool with one parameter and annotations covering destructive and idempotent hints, the description is adequate. It could mention that the team must exist or that deletion is irreversible, but not required for basic usage.

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 coverage is 100% with teamId description. The description repeats the parameter name and required flag but adds no extra meaning beyond the schema. Baseline of 3 is appropriate.

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 clearly states 'Delete a team (admin).' The verb 'delete' and resource 'team' are specific. It distinctively separates from sibling tools like create, get, update, list, etc.

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?

The description mentions it's an admin tool but provides no guidance on when to use this tool versus alternatives (e.g., when to delete vs. update or archive). No explicit when-not or alternatives.

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