Contract Testing: Admin Update Role

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

Description accurately indicates a mutation operation ('update'). However, annotations set readOnlyHint: true, which contradicts the write operation. The description does not disclose additional behavioral traits such as permission requirements or idempotency.

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 structured with a title, toolset label, and parameter list, but it redundantly lists parameters already in the schema. The parameter block takes up space without adding value.

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?

The description omits usage context, output expectations, and error scenarios. Given the contradiction with annotations and lack of output schema, the description provides insufficient context for an agent to use the tool correctly.

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%, so parameters are documented. The description restates them without adding new semantic meaning beyond what the schema provides (e.g., types, requirements). No extra context on allowed values or constraints.

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?

Description clearly states 'Update an existing role's name and permissions (admin)', specifying the verb (update) and resource (role). This distinguishes it from sibling tools like create_role and 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 on when to use this tool versus alternatives like create_role or list_roles. The description lacks context for selection, leaving the agent to infer from sibling names.

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