Contract Testing: Publish Consumer Contracts

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds that contracts are 'published with branch and tag metadata', which is consistent but does not disclose additional behavioral traits (e.g., whether it overwrites, triggers verifications). No contradiction with annotations.

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 short, with a clear main sentence and a parameter list. The structure is logical, but the parameter list is redundant given the schema. No wasted words, but could be more concise by omitting the parameter details.

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 is a simple publish action with no output schema. The description does not mention return values or side effects (e.g., that contracts become available for verification). Annotations cover idempotency and non-destructiveness, but the description could benefit from mentioning the outcome of successful publication.

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 has 100% description coverage for all parameters. The description's parameter list essentially duplicates the schema descriptions without adding new semantics. For example, 'contracts' is described as 'Contracts to publish' in both places. The description adds no extra meaning beyond what the schema provides.

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 ('publish'), the resource ('consumer Pact contracts'), and the destination ('Pact Broker or PactFlow'). It also mentions the ability to include metadata (branch, tags). This distinguishes it from sibling tools like 'contract-testing_publish_provider_contract' and 'contract-testing_can_i_deploy'.

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 does not explicitly guide when to use this tool versus alternatives. It only states the action and parameters. While the toolset grouping ('Contracts') hints at its category, there is no 'when to use' or 'when not to use' advice, nor mention of alternatives among sibling tools.

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