list_all_project_test_cases

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

Discloses pagination strategy, merging, and deduplication logic. With no annotations, this adequately informs the agent of key behaviors. Could mention read-only nature or error handling.

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?

Two concise sentences, front-loaded with purpose and behavior. No unnecessary 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?

Covers main purpose and behavior. With 5 parameters and no output schema, description is mostly complete but could mention edge cases like empty results or behavior when dedup key is absent.

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 coverage is 100%, so baseline 3 applies. Description adds no parameter-specific details beyond the schema; it only contextualizes the overall behavior.

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?

Description clearly states 'Fetches all pages' and specifies merging and deduplication. Distinguishes from sibling tools like search_test_cases (single page) and list_cycle_test_cases (cycle-specific).

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?

Explicitly says 'Use for exporting or counting beyond a single page', providing clear context. Mentions stop condition (short page or maxPages) but lacks explicit when-not or alternative tools.

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