get-test-case

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

No annotations provided, so the description carries full burden. It only states 'Get test case details' without disclosing what happens on missing UUID, error handling, or effects of include/fields parameters. Read-only assumption is implied but not explicit.

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?

A single, front-loaded sentence efficiently conveys the core action. However, it may be overly concise, missing valuable context. Every word earns its place but more could be added.

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?

No output schema, no annotations, and 3 parameters with little explanation. The description fails to cover return types, error scenarios, or how the 'include' and 'fields' parameters affect results. Incomplete for a real-world tool.

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 67% (2 of 3 params described). The description adds no parameter details beyond the schema; 'by UUID' merely restates the id field's schema description. The include and fields parameters are not explained.

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 'Get test case details by UUID' clearly specifies the verb (get), resource (test case), and identifier method (UUID). Among siblings, there is get-test-case-by-name, so this distinguishes by UUID lookup.

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 guidance on when to use this tool versus alternatives like get-test-case-by-name. No context about prerequisites or exclusions; usage is only implied.

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