Contract Testing: Admin List Roles

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

Annotations already convey readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the administrative scope context, which implies authorization needs. This adds some value beyond the annotations, though it does not elaborate on behavioral details like pagination or response format.

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: one sentence with the core action plus a toolset label. No unnecessary words, and the primary verb is front-loaded. Every element earns its place.

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?

For a parameterless list operation with strong annotations, the description covers the essential purpose. However, it omits details about the response structure (e.g., what fields are returned, pagination) which would be helpful given no output schema. Still sufficient for an agent to invoke 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 description coverage is 100% as there are zero parameters. The description redundantly states 'Parameters: None' but does not add meaning beyond the schema. Baseline score of 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 the tool's purpose: 'List all roles defined in the workspace (admin).' It uses a specific verb ('list') and resource ('roles') and distinguishes itself from sibling tools like contract-testing_admin_get_role and contract-testing_admin_create_role. The admin qualifier adds clarity on scope.

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, such as contract-testing_admin_get_role for a specific role or contract-testing_admin_list_permissions for permissions. There is no explicit context or exclusion criteria.

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