qase_case_upsert

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

Annotations already indicate readOnlyHint=false (write operation) and destructiveHint=false. The description adds valuable context about the conditional create/update behavior and the server-side normalization of enum labels/IDs, which goes beyond the structured annotations. No contradictions with annotations.

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 two sentences, front-loaded with the core action, and provides precisely the essential information about upsert behavior and enum flexibility. No wasted words or redundant repetition of schema fields.

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 the tool's complexity (21 parameters, nested objects, no output schema), the description is functional but sparse. It covers the primary upsert behavior and enum normalization, but does not mention the required `code` and `title`, the nested step structure, or expected response shape. The schema fills many gaps, but a richer description would improve completeness.

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?

With only 48% schema description coverage, the description partially compensates by explaining that enum fields accept both labels and numeric IDs. However, it does not add detail for the many other undocumented parameters, leaving the schema descriptions to carry most of the burden. The added enum guidance is useful but limited.

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 opens with 'Create or update a test case,' which is a specific verb+resource pair that clearly identifies the tool's function. It further specifies the behavior based on the presence of `id`, distinguishing it from sibling tools like defect or run upserts.

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 gives clear context on when to use upsert semantics (update if `id` provided, create otherwise). It does not explicitly mention alternatives or exclusions, but the resource is unambiguous, and sibling tool names already imply distinct purposes.

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