Contract Testing: Admin Reset Roles

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

The description says 'Reset all roles' implying a write/modification operation, but annotations set readOnlyHint=true, indicating read-only. This is a clear contradiction between description and annotations, severely undermining transparency.

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 extremely concise at one sentence plus a toolset indicator and parameter note. It is front-loaded and every part is essential, though the parameter line is redundant but short.

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?

Despite the simple nature (no parameters, no output schema), the description fails to properly inform the agent due to the annotation contradiction, making it misleading. It also lacks any behavioral details beyond the basic action.

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?

With schema coverage at 100% (empty schema) and zero parameters, the description only redundantly states 'Parameters: None'. It adds no new semantic meaning beyond the input schema.

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 'Reset all roles to their factory defaults (admin)', specifying a specific verb and resource. This distinguishes it from sibling tools like contract-testing_admin_create_role or contract-testing_admin_delete_role.

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 is given on when to use this tool versus alternatives, nor any warnings about consequences. The description only states what it does without context for appropriate usage.

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