Contract Testing: Admin Delete Role

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not say whether deletion is irreversible, what happens to users currently holding the role, or whether it fails if the role is still assigned — the exact context annotations cannot express.

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 operative sentence is front-loaded and short. The markdown scaffolding ("Toolset: Admin", "Parameters:") mostly duplicates structured fields and could be dropped, but it is not verbose enough to obscure the core action.

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?

An output schema exists and there is only one clearly documented parameter, so the call mechanics are fully covered. What is missing is consequence information for a destructive role deletion, which is the meaningful remaining gap for a mutation tool.

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 single roleId parameter is already documented as "UUID of the role" in the schema. The description restates that verbatim, adding no format, sourcing, or validation meaning beyond the schema, so baseline 3 applies.

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 gives a specific verb and resource ("Delete a role") and scopes it to the admin surface. It does not, however, explicitly contrast with the nearby siblings such as contract-testing_admin_update_role, contract-testing_admin_get_role, or contract-testing_admin_reset_roles, so an agent must infer the boundary from the verb alone.

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?

There is no when-to-use guidance, no prerequisites (e.g. admin permissions), and no mention of alternatives or when not to delete. The agent learns only that this is an admin delete operation, not the conditions under which it should be preferred over updating or resetting roles.

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