Get test case detail

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

Discloses read-only nature and specific behavior: preserves steps with empty expected results. With no annotations, description carries burden well. Could mention more about response structure or authorization, but adequate for a read tool.

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 concise sentences front-load purpose and add key behavioral detail. Every word earns its place.

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?

Covers returned content (steps, expected results) and behavioral nuance. Lacks mention of other possible fields (status, metadata), but sufficient for single-parameter tool with no output 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 100% with description and pattern. Description adds only an example key, but no new semantic info beyond schema. Baseline score 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?

Clearly defines verb 'Returns' and resource 'full detail of a single Zephyr test case', including specific content like ordered steps. Distinguishes from siblings that list or search test cases.

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?

No explicit when-to-use or alternative guidance. Usage is implied (when full details needed), but description does not contrast with sibling tools like list_story_test_cases or search_test_cases.

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