list_test_cases

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The word 'List' implies a read-only operation, and the filter options give some behavior, but it does not disclose return format, pagination, permission requirements, or any side effects. This is a moderate gap for a tool with no output schema.

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 long, front-loaded with the core action and resource, followed by a concise list of filter options. Every word contributes value, with no redundancy or unnecessary detail.

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 list tool with a required project parameter and multiple optional filters, the description covers the main purpose and filter capabilities. However, without an output schema, it does not mention what fields are returned, whether pagination exists, or any usage constraints. It is adequate but leaves important context undeclared.

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 description coverage is only 40%, so the description should compensate. It adds meaning by identifying feature, type, priority, and status as optional filters, and project is implied as the scope. However, it does not elaborate on allowed values or defaults, and the schema already provides enums for three parameters. It provides some additional context but not enough to fully compensate for the low schema coverage.

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 uses a specific verb 'List' with the resource 'test cases for a project' and explicitly mentions optional filters, making it clear what the tool does. It distinguishes itself from sibling tools like 'generate_test_cases', 'add_test_case', and 'list_projects' by focusing on listing existing test cases.

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 establishes clear context: this tool is for listing test cases under a project, with optional filters. While it does not explicitly contrast with alternatives or state when not to use it, the purpose itself implies its usage scenario and separates it from generation, updating, or project-level listing.

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