Contract Testing: Get BDCT Provider Contract

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that it is for Bi-Directional Contract Testing, but no further behavioral traits (e.g., error handling, performance) are disclosed. This meets the baseline expectation for safe, idempotent read operations.

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 front-loaded, stating the core purpose in the first sentence. However, the inclusion of 'Toolset:' and 'Parameters:' lines adds redundancy, though not harmful. Could be slightly more succinct.

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 fetch operation with well-annotated idempotent behavior, the description is complete enough. It specifies what is being fetched (OpenAPI contract) and the required parameters. The absence of an output schema is mitigated by the clear statement about fetching a contract. It meets needs for selection and basic invocation.

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 input schema fully describes both parameters (providerName, providerVersionNumber). The description repeats the parameter names and types, adding no additional semantic meaning beyond what the schema provides. With 100% schema coverage, a 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 fetches the provider OpenAPI contract for a given provider version. It distinguishes from sibling tools like get_bdct_consumer_contracts, but could be more precise by mentioning the context of Bi-Directional Contract Testing is already part of the process.

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, such as get_bdct_consumer_contracts or get_bdct_provider_contract_verification_results. The description does not provide context for optimal usage or exclusions.

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