Contract Testing: Admin Add Role to User

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

The description contradicts annotations: it says 'Add' (write operation) but annotations mark readOnlyHint=true. No additional behavioral context is provided beyond the misleading information.

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 concise and includes a helpful 'Toolset: Admin' label. However, it repeats parameter information already in the schema, which is slightly redundant but not overly verbose.

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 high schema coverage and annotations, the description omits usage guidelines and contains a contradiction. It does not explain expected outcomes (no output schema) or when to use this tool, leaving gaps for an AI agent.

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 merely repeats the parameter names and types from the schema without adding new semantic meaning. No extra value beyond what the schema already provides.

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 the action 'Add a single role to a user (admin)' with a specific verb and resource, and it distinguishes from sibling tools like 'contract-testing_admin_remove_role_from_user' and 'contract-testing_admin_set_user_roles'.

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 (e.g., set_user_roles or remove_role_from_user). The description lacks context about prerequisites or conditions for use.

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