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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety needs no restating. The description adds genuinely useful behavior beyond that: rows are a compact shape missing steps/expected result, rows carry storyId, and page/limit defaults with a hard max of 50. Pagination metadata (total counts, sort order) remains undisclosed.

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?

Four short sentences, front-loaded with purpose and filters before the routing hint and defaults. The storyId/coverage note and the compact-shape warning each carry distinct decision-relevant information, so nothing reads as filler.

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 9-parameter read tool with no output schema, the description covers purpose, filter set, response shape and the escape hatch to the detail tool. The remaining gap is pagination behavior (ordering, total count) which an agent paging past 50 results would want.

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 56% schema coverage, the description partly compensates by enumerating the filter set (suiteId, storyId, status, type, assigneeId, title search) and stating page/limit defaults and the 50 cap. However, it mostly echoes schema property names and adds no semantics for the enum values or how filters combine, so it is baseline-adequate rather than additive.

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?

States a specific verb and resource ('List test cases in a Stride project') plus the filter surface, so the agent knows exactly what it retrieves. It also explicitly contrasts itself with stride.get_test_case, which returns full steps and expected result, making the boundary between the two unambiguous.

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?

Names the alternative tool and the condition that selects it ('use stride.get_test_case for full steps + expected result'), and signals that this list is sufficient for coverage questions via storyId. It stops short of covering adjacent alternatives like list_test_suites or list_test_runs, so it is clear but not exhaustive.

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