Contract Testing: Delete Pacticipant

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

Annotations already signal destructive behavior, and the description usefully adds that deletion cascades to 'all its associated data.' This is important behavioral context beyond the structured annotations, even though permissions or irreversibility are not explicitly mentioned.

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 core action and its destructive scope. The parameter list is clear, though it largely duplicates the schema and the 'Toolset: Pacticipants' line adds limited value, keeping it just below a top score.

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 single-parameter destructive operation, the description plus annotations covers the essential facts: what is deleted, that the operation is destructive, and that it is idempotent. Lack of an output schema is not a major gap for a simple delete operation, though more detail on permissions or irreversibility would improve 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 description coverage is 100%, and the description essentially repeats the schema's parameter documentation. It adds no new semantic meaning beyond what the input schema already provides, so the 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 states a specific verb ('Delete') and resource ('pacticipant') and clarifies scope with 'all its associated data.' This distinguishes it from other deletion tools like delete_branch or delete_webhook and makes the tool's exact purpose 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?

Usage is implied by the name and description: use this when the pacticipant should be permanently removed. However, there is no explicit guidance about when not to use it, such as preferring update_pacticipant or considering downstream impacts before deletion.

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