Contract Testing: Publish Provider Contract

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that this publishes to PactFlow under BDCT, but says nothing about authentication needs, whether re-publishing a version overwrites prior contract data, or what failures look like — meaningful gaps for a write operation.

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 front-loaded and states purpose efficiently. The subsequent parameter block largely duplicates the input schema, which is redundant bulk, though it remains scannable and does not obscure the core statement.

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 nested-object, 6-parameter mutation tool this covers the shape of the call, and the existence of an output schema means return values need no explanation. However, nothing is said about prerequisites, versioning semantics, or how publishing interacts with consumer contracts in BDCT, leaving the agent under-informed about consequences.

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% and the nested contract object (content, contentType, specification, selfVerificationResults) is fully documented in the schema, so the baseline of 3 applies. The description's parameter list only restates the schema's own field descriptions without adding format, encoding, or validation guidance.

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?

States a specific verb (publish) plus resource (provider OpenAPI/AsyncAPI contract with self-verification results) and names the target system (PactFlow, Bi-Directional Contract Testing). The 'provider' qualifier cleanly separates it from the sibling contract-testing_publish_consumer_contracts.

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 Bi-Directional Contract Testing framing implies when the tool applies, but the description never states prerequisites (API token, existing provider/pacticipant) nor points to the get_bdct_provider_contract or publish_consumer_contracts siblings as alternatives or follow-ups. Usage is inferable rather than explicit.

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