Contract Testing: Admin Get Role

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description states 'Retrieve details' which aligns with these annotations. No additional behavioral context is added beyond what annotations provide.

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 brief, but includes a redundant 'Toolset: Admin' heading. The parameter listing is concise. Overall, it is efficient but could be more structured, e.g., removing the redundant toolset line.

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 tool has no output schema, yet the description does not explain the return structure of role details. For a simple read operation, it is somewhat complete but lacks information about the response format or permissions needed.

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?

The description's parameter section repeats the schema exactly (roleId: UUID of the role). Schema coverage is 100% and the description adds no new meaning. Baseline 3 is appropriate.

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 'Retrieve details for a specific role by UUID', specifying the action (retrieve), resource (role), and identifier (UUID). It distinguishes from siblings like `contract-testing_admin_list_roles` (list all) and `contract-testing_admin_create_role` (create).

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?

The description provides no guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or context are given. The only hint is 'Toolset: Admin' which is already in the title.

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