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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered externally. The description adds nothing beyond that: it says nothing about default limit of 100, offset-based pagination, whether all results are returned or truncated, or the shape of results.

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?

Six words with the resource front-loaded and no filler, so nothing is wasted. But the brevity comes from under-specification rather than efficiency; the single sentence carries almost no operational content.

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?

There is no output schema, so the description would normally need to describe the return shape, and it does not. For a paginated list tool in a large test-management toolset, missing pagination defaults, ordering, and sibling differentiation leaves material gaps.

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 25% — only the context parameter is documented, while limit, offset, and project_id are bare types. The description mentions a project scope, weakly implying project_id, but does not compensate for the undocumented pagination parameters at all.

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 gives a specific verb ("List") and resource ("test cases") scoped to a project, which is enough to understand the basic operation. It does not distinguish this from the sibling search_test_cases, leaving the agent to infer the difference between a plain listing and a search.

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?

"List test cases for a project" states no conditions for use and names no alternative. With search_test_cases and get_test_case both available, an agent gets no signal about when this enumeration is preferred over searching or fetching a single case.

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