Contract Testing: Delete Pacticipant

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

The description claims deletion (destructive action) but annotations set destructiveHint=false and readOnlyHint=true, creating a direct contradiction. This severely misleads the agent about the tool's behavior.

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?

Very concise: two short sentences plus a parameter list. The structure is clear, though the 'Toolset: Pacticipants' line adds minimal value. No unnecessary words.

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 deletion tool, the description lacks critical context: what happens to associated data (irreversible?), any recovery options, required permissions, or side effects. The contradiction with annotations further reduces completeness.

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% but the description merely repeats the schema's parameter description ('Name of the pacticipant to delete') and adds a 'required' tag, adding no meaningful extra semantics.

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?

Clearly states 'Delete a pacticipant and all its associated data.' The verb (delete) and resource (pacticipant) are explicit. However, it does not differentiate from sibling mutation tools like patch or update for pacticipants.

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 tool versus alternatives, nor any prerequisites or context (e.g., permissions needed). The description only states the action without usage context.

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