Contract Testing: List Pacticipants

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

Annotations already communicate read-only, idempotent, non-destructive behavior. The description adds useful scope context (Pact Broker or PactFlow workspace, 'all' pacticipants), but does not disclose pagination behavior, ordering, or any access requirements beyond what the schema defaults imply.

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 direct and front-loaded, and the overall length is short. The separate 'Parameters' section duplicates schema information and the 'Toolset' line adds little, which prevents a top score.

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 read-only listing tool with two optional pagination parameters, the essential facts are present. However, with no output schema, the description does not describe the shape of the returned pacticipant objects, and 'all' could be misinterpreted as a single non-paginated response despite the pageSize/pageNumber defaults.

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 already describes both parameters fully with defaults, so schema coverage is 100%. The description merely repeats the same parameter text and adds no extra constraints, formatting details, or interaction notes such as maximum page size.

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 states a specific action ('Retrieve'), a specific resource ('pacticipants'), and clarifies what they are ('applications/services'), plus the workspace scope. It does not explicitly differentiate this from sibling tools like list_pacticipants_by_label or get_pacticipant, so it stops short of a 5.

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 purpose statement implies this is the tool to use when you need the full set of pacticipants, but there is no explicit guidance on when to use it versus alternatives or when not to use it. The 'Toolset: Pacticipants' line is organizational rather than usage guidance.

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