Get Manual Test Case

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

Annotations already declare readOnlyHint=true, but the description adds real behavioral detail beyond that: version history and execution results are read-only and cannot be mutated, and comments/linked issues are added through update_manual_test_case instead. This clarifies the mutation boundary that the bare annotation does not, though it says nothing about result size, pagination, or auth needs.

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?

Front-loads what the tool returns, then moves to the caseId affordance and the read-only/mutation boundary. Four sentences, all functional, though the opening enumeration is dense and the caseId sentence partially duplicates the schema.

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?

With no output schema, the description carries the burden of describing the return payload, and it does so thoroughly (including activity sub-collections). It is nearly complete for a 2-param read tool; only pagination/volume behavior for 'execution results across all manual runs' is unaddressed.

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%, so both parameters (caseId, projectId) are already documented. The description's note that caseId accepts either the internal _id or a 'TC-123' style ID merely restates the schema, adding no syntax or constraint the agent cannot already read. Baseline 3 applies.

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?

Specific verb+resource ('Get the full details of one manual test case') followed by an explicit field enumeration (steps, preconditions, postconditions, metadata, linkedIssues, activity). The 'one' scope implicitly separates it from list_manual_test_cases, but the sibling is never named, so the differentiation is left to inference rather than stated.

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?

Gives a clear workflow directive: 'Call this before update_manual_test_case to see current steps, comments, and linked issues before modifying them.' That is actionable context for when to reach for this tool. It does not state when NOT to use it (e.g., enumerating many cases), so it stops short of a 5.

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