List Test Cases

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 tool's safety is clear. The description adds context about paginated results and returned fields (IDs, names, tags), but does not reveal any additional behavioral traits beyond what annotations and schema imply. This is adequate but not exceptional.

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 two sentences: the first states the core function, the second adds purpose. No wasted words, front-loaded with key information. It is appropriately sized and easy to parse.

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 presence of an output schema and high parameter coverage, the description is largely sufficient. It explains the tool's purpose and pagination, but could mention default behavior (e.g., returns all cases if no filters applied) or the fact that page/size defaults are 0 and 20 (though already in schema). Overall, complete enough for a list tool.

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?

With 100% schema description coverage, the baseline is 3. The description does not add parameter-specific meaning beyond what the schema already provides. It mentions pagination and returned fields but does not elaborate on how parameters like 'tags' or 'status' work (exact match is already in schema). Thus, no extra value.

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 it lists test cases in a project, specifying the verb 'List' and resource 'test cases'. It mentions the return fields (IDs, names, tags) and pagination. However, it does not explicitly differentiate from the sibling tool 'search_test_cases', which could be seen as a more filtered variant.

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 advises 'Use this to review existing test documentation', giving a general usage context. But it lacks explicit when-not-to-use guidance or mention of alternatives like 'search_test_cases' for complex filtering or 'get_test_case_details' for single case details.

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