Contract Testing: Delete Pacticipant

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description merely confirms the deletion. It adds the detail that 'all associated data' is deleted, which is useful but not beyond what annotations imply. No contradictions.

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 three brief lines: a sentence, a toolset label, and a parameter list. It is front-loaded with the core action. The toolset line adds some context but is not strictly necessary, though it does not waste 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 simple delete tool with one parameter and no output schema, the description covers the essential information: what it deletes and that data is permanently removed. No missing critical details, but could mention irreversibility explicitly.

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%, and the description repeats the parameter 'pacticipantName' with the same description as the schema. No additional meaning or constraints are provided beyond what the schema already conveys.

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 pacticipant and all its associated data.' The verb 'delete' and resource 'pacticipant' are explicit, and the scope 'all associated data' adds precision. Among siblings, there are many pacticipant-related tools (create, update, get, list, etc.), making this distinction clear.

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 vs alternatives. There is no mention of prerequisites, consequences, or when not to use it. With many delete tools among siblings (e.g., delete_environment, delete_webhook), the description provides no context for appropriate invocation.

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