Test Case

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

Beyond annotations (destructiveHint=true), the description explicitly warns that delete is destructive and requires confirmation, clarifies that create does not auto-run the test, and mentions soft-delete. This adds valuable behavioral context, though it does not cover rate limits or authorization.

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 extremely concise and well-structured: a one-sentence overview followed by clear action-specific bullet points. Every sentence adds value, with no unnecessary content. The front-loaded purpose immediately orients the agent.

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 12 parameters, 3 actions, and no output schema, the description covers the parameter requirements well but omits return values for create, update, and delete. The absence of output schema documentation is a gap, though annotations partially compensate for behavioral hints.

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?

The description groups parameters by action, showing required combinations (e.g., suiteUuid or suiteName+project for create). While the schema already uses action-prefixed descriptions, the description's structured grouping significantly aids understanding. Baseline 3 due to 100% schema coverage, but extra value raised score.

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 tool manages test cases within a suite and enumerates three actions (create, update, delete) with specific parameter requirements. It distinguishes itself from sibling tools like test_suite and executions by focusing on individual test case operations and noting that create does not auto-run.

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 provides implicit usage guidance through action-specific parameter lists (e.g., suiteUuid vs. suiteName+project for create), but does not explicitly state when to use this tool over alternatives like test_suite or executions. No direct comparison to siblings is provided.

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