Contract Testing: Admin Delete Role

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

The description 'Delete a role' contradicts annotations that mark readOnlyHint=true and destructiveHint=false. Deletion is a destructive operation, making the annotations misleading. The description fails to disclose actual 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 short but repeats parameter info already in schema. Could be streamlined but overall efficient.

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?

Minimal description for a simple tool, but the annotation contradiction undermines trust. No mention of consequences, permissions, or reversibility.

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?

One parameter 'roleId' with schema description 'UUID of the role'. The description repeats this exactly, adding no extra meaning. Baseline 3 due to full schema coverage.

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 'Delete a role (admin)', which clearly indicates the verb and resource. However, it does not differentiate from sibling tools like 'create_role' or 'update_role' beyond the name.

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, prerequisites, or when not to use it. No mention of alternatives or context for deletion.

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