Test Case

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. Description adds that delete is a soft-delete requiring confirmation, and create does not auto-run. No contradictions.

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?

Well-structured with bullet points separating actions. Efficiently communicates purpose and per-action details. Slightly lengthy but every sentence provides necessary context.

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 all three CRUD operations with parameter constraints. Without output schema, omission of return values is acceptable. Includes important behavioral notes like soft-delete and no auto-run.

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?

Input schema covers all parameters (100% coverage). Description adds value by grouping parameters per action and clarifying conditional requirements (e.g., 'requires a project identifier' for suiteName).

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 'Manage individual test cases within a suite' and enumerates three actions (create, update, delete) with specific resources. It distinguishes from siblings like test_suite by focusing on test case CRUD.

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?

Explicitly lists actions and their required/optional parameters. Notes that create does not auto-run and delete is destructive requiring confirmation. Lacks explicit comparison to sibling tools but usage context is clear.

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