Contract Testing: Publish Consumer Contracts

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the destination (Pact Broker/PactFlow) and metadata capabilities, but it does not disclose overwrite behavior, authentication needs, or other side effects. This is enough to slightly raise it above baseline, but not by much.

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 opening sentence is crisp and front-loaded, but a large parameter block repeats the schema almost word-for-word. Given that a complete schema is already provided, this duplication is unnecessary and makes the description longer than it should be. The parameter list does not earn 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?

The description plus schema provide enough to call the tool correctly, including required parameters, types, and nested contract object structure. Minor gaps remain: no mention of authentication, return values, or the relationship between pacticipantName and the contracts' consumerName. These omissions are not severe given the annotations.

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 six parameters are fully documented in the input schema. The description's 'Parameters' section is essentially a verbatim copy of the schema's descriptions and adds no new meaning beyond human-readable formatting. Baseline 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 uses a specific verb ('Publish') and names the exact resource ('consumer Pact contracts') and destination ('Pact Broker or PactFlow'). It also mentions branch and tag metadata, clearly distinguishing it from provider-side contract publishing by explicitly saying '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?

No guidance is given on when to use this tool versus alternatives. It does not mention the sibling contract-testing_publish_provider_contract or any other Pact tools, and there are no conditions or exclusions. The only context is the generic 'Toolset: Contracts' label, which is too weak to route an agent effectively.

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