list_differential_pairs

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'normalized' but does not explain what that entails, nor does it state whether the operation is read-only, how pagination works, or any potential side effects. The description is minimal and leaves these aspects unclear.

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 a single sentence of 10 words, front-loaded with the action verb 'List'. It is concise and contains no extraneous information.

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 straightforward list operation, and an output schema exists, so return values need not be described. However, the description lacks details about what 'normalized' means, how the path parameter should be used, and how this differs from related list/analysis tools. Given the low schema coverage and lack of annotations, the description is only partially complete.

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 descriptions are 0% covered, so the description should compensate. It does not explain the 'path' parameter beyond implying a DipTrace project, nor the 'limit'/'offset' pagination parameters. The description adds minimal value over the raw schema.

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 ('List') and the specific resource ('normalized DipTrace project differential pairs and their rules'). It distinguishes from sibling tools like get_differential_pair (singular fetch) and analyze_differential_pairs (analysis).

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 implies when to use the tool (when you need a list of differential pairs), but it does not explicitly mention alternatives or when-not-to-use conditions. Sibling names suggest distinctions, but no direct comparison is provided.

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