Contract Testing: Get BDCT Consumer Contract Verification Results

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint, covering safety. The description adds no behavioral details beyond the fetch action. It does not contradict annotations, so a 3 is appropriate.

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 with a single sentence and a structured list of parameters. It is front-loaded and avoids verbosity. Minor redundancy with schema but efficient.

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 good annotations and full schema coverage, the description lacks information about the return value (e.g., format, content of verification results). Without an output schema, this is a gap for agent understanding.

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 baseline is 3. The description lists parameters with the same descriptions as the schema, adding no additional meaning or context.

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 ('Fetch'), the object ('consumer contract verification results'), and the context ('for a given provider version in Bi-Directional Contract Testing'). It distinguishes from the sibling tool that fetches provider contract verification results by specifying 'consumer'.

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 implies usage when consumer contract verification results are needed for a provider version in BDCT, but it does not explicitly state when to use this tool over alternatives (e.g., get_bdct_provider_contract_verification_results) or provide exclusions or prerequisites.

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