get_case_execution_history

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

Annotations already flag readOnly, idempotent, and non-destructive, so the description doesn't need to repeat safety. It adds useful context about the 'manual' scope and return contents ('pass rate and execution timeline'), but doesn't disclose additional behavior such as how far back it looks or how results are paginated. No contradiction with annotations.

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 a single, front-loaded sentence with no filler. It efficiently communicates what the tool returns, the scope, and the type of executions included.

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, but the description tells the agent at a high level what comes back (pass rate and execution timeline) and covers the full scope of what is retrieved. The parameter schema covers the other details. It could be slightly more explicit about the response shape, but for a simple read tool it is adequate.

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 100% and the parameter descriptions are already rich, including the important caseId vs TC-N distinction. The description does not add parameter-level value beyond what the schema provides, so the baseline 3 is appropriate.

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 ('Get') and resource ('manual execution history for a test case') and clearly scopes it 'across all test runs' and 'both standalone executions and release test runs'. It does not explicitly distinguish itself from siblings such as get_test_history, so it is clear but not a full 5.

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 'manual' qualifier and the mention of both standalone and release test runs imply when this tool is relevant, but there is no explicit guidance about alternatives or when this tool should not be used. It gives context without stated exclusions.

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