Get Test Manager Test Execution History by Jira ID

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

No annotations provided, so description carries full burden. It explicitly states 'Read-only; does not modify anything', and discloses behavior for missing data ('returns an empty history rather than an error'). This provides clear expectations without 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?

Two sentences: first details what is retrieved and the output fields, second states usage and behavior (empty history, read-only). No fluff, all information earns its place, front-loaded with key action.

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?

Given one parameter, no output schema, and no annotations, the description provides rich detail: output fields, error handling, read-only nature, and usage context. It is fully adequate for correct tool selection and invocation.

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?

Only one parameter `jira_issue_id` with 0% schema description coverage. The description adds value by explaining the format ('e.g. 'PROJ-123'') and context, which is not present in the schema (only type and required). This compensates for the lack of schema description.

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 clearly states the verb 'Retrieves' and resource 'execution history of every LambdaTest Test Manager test case linked to a given Jira issue ID', provides an example format ('PROJ-123'), and lists output fields. It distinguishes from sibling `get_testExecutionHistoryByTestCaseId` by specifying Jira ID linkage.

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 explicitly tells when to use ('Use this to see how all test cases tied to a Jira ticket have performed') and describes behavior when no linked executions (returns empty history, not error). While it does not explicitly state when NOT to use or suggest alternatives, the purpose is clear enough to differentiate from sibling tools.

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