Contract Testing: Get BDCT Consumer Contracts

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description's 'Fetch' is consistent with those. The description adds little beyond that—no notes on pagination behavior, response content, or provider-version semantics.

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 main sentence is appropriately terse and front-loaded. The repeated Parameters section is redundant with the provided input schema and adds length without 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?

For a simple read-only fetch with only four flat parameters, the description plus schema is sufficient to determine required inputs and defaults. It doesn't describe return structure, but the purpose statement makes the expected result clear enough.

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%, so all four parameters are already documented. The description's Parameters block simply repeats the schema text and adds no additional semantic meaning.

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 opening sentence names a concrete operation ('Fetch all consumer Pact contracts') and scopes it to a provider version in Bi-Directional Contract Testing. It is clear but does not explicitly contrast with sibling tools such as get_bdct_consumer_contract_verification_results, relying on the word 'contracts' to differentiate.

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 use when BDCT consumer contracts for a provider version are needed, and the Toolset label adds context. It provides no exclusion criteria or explicit alternatives among the many sibling tools.

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