post_test_case

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent behavior, so the safety profile is partly covered. The description adds nothing beyond that — no note on permissions, what gets created, side effects, or validation, leaving the annotation-covered behavior undisclosed.

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?

It is short, but the second sentence is pure redundancy that repeats the first verbatim in slightly different words, so not every sentence 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?

For a mutating, open-world creation tool with a rich nested body and no output schema, the description omits required-field expectations, side effects, and the relationship to project/folder scoping. It is too thin for the tool's complexity.

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 tool takes a single nested body object with many documented properties in the schema, yet the description says nothing about the required project_id/name fields or any parameter semantics. It contributes zero meaning beyond the structured schema.

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 names a clear verb and resource ('Create a test case') and adds scope ('within a project'), so the basic action is unambiguous. However, the second sentence merely restates the first, and nothing distinguishes this from sibling creation tools such as put_test_case or post_batch_update_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?

There is no guidance on when to use this tool versus alternatives like put_test_case (update) or the batch variants, and no mention of prerequisites. The 'within a project' clause implies scope but not usage conditions.

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