Contract Testing: Review Pact Tests

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that this is an AI-assisted review and hints at producing recommendations, but it does not describe what the tool returns, whether results are immediate, or how the review is structured.

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 concise, but the description includes a redundant 'Toolset: Review Pact Tests' heading and a full parameter list that duplicates the input schema. These parts do not earn their place and add unnecessary length.

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 input parameters are well documented in the schema, but there is no output schema and the description does not explain what the agent should expect in response. With five parameters, nested objects, and no return-value information, the description is incomplete for confidently using the tool's result.

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 the schema already documents all parameters and nested fields. The description's parameter list largely duplicates the schema without adding meaningful new meaning or clarifying the optional openapi structure.

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 identifies the action ('Review Pact tests') and the subject ('Pact tests using PactFlow AI'), so an agent can understand what the tool does at a glance. It does not explicitly differentiate from the closely related sibling 'contract-testing_generate_pact_tests', so it misses the top score.

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?

There is no guidance on when to use this tool versus alternatives such as contract-testing_generate_pact_tests, nor any statement of when not to use it. The description lists inputs but does not explain the decision context for choosing this tool.

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