list_test_cases

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

With no annotations provided, the description must fully disclose behavioral traits. The minimal description 'List test cases for a project' gives no information about pagination, sorting, default behavior when no parameters are provided, or any side effects. This is insufficient for an agent to understand the tool's behavior.

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 extremely concise (one sentence) but at the cost of essential information. For a tool with 7 parameters and many siblings, a single sentence fails to provide adequate guidance. Conciseness should not compromise completeness; this is under-specification, not conciseness.

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?

Given the complexity (7 parameters, no output schema, no annotations), the description is grossly incomplete. It does not mention pagination behavior, default sorting, or how to effectively use the parameters. The agent has insufficient information to correctly invoke this tool without relying on external knowledge or trial and error.

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 covers 71% of parameters with descriptions, but the tool description adds no additional meaning beyond the schema. For example, it does not clarify how 'search' interacts with other parameters or suggest typical combinations. The description should have added context like 'Use search for text filtering across test case names' to compensate for low-enrichment.

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 'List test cases for a project' clearly states the action (list) and resource (test cases), and implies scope (for a project). It is specific and uses a verb+resource structure. However, it does not differentiate from sibling tools like 'search_test_cases' or 'list_test_results', which could cause confusion about when to use this tool.

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 provides no guidance on when to use this tool versus alternatives such as 'search_test_cases'. It lacks any explanation of prerequisites, typical use cases, or exclusions, leaving the agent to infer usage from the name alone.

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