get_execution_cases

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

Annotations already confirm read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond those annotations: it documents the returned fields, notes that externalLinks appear only with integrations:read, and guarantees that 'everything report_case_result writes reads back here.'

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 dense but all information is relevant: purpose, return contents, dependency note, workflow ordering, and filtering. The first sentence packs in much detail while still being readable, and the later sentences sharpen the workflow context without redundancy.

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 read-only list tool with no output schema, the description does an excellent job explaining the response structure and filtering. Minor missing context: exactly how pagination is represented in the response and what valid values exist for status beyond the examples in the schema.

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 coverage is high (67%), with useful descriptions already on search, status, groupId, and executionId. The description contributes only the mapping of 'filtering by ... title' to the search parameter, while limit/offset are standard unannotated parameters.

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 an explicit action ('List'), a specific resource ('individual case-run rows of a Manual Test Execution'), and the intended use ('so you can report results against them'). It also clearly distinguishes itself from report_case_result by positioning itself as the read-side counterpart.

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?

Provides explicit workflow positioning: 'Use after add_*_to_execution and before report_case_result.' This tells the agent exactly when in a process the tool fits, and the read-back note clarifies its relationship to report_case_result.

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