create_test_case

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

With no annotations carrying behavioral hints, the description supplies needed transparency: it discloses auto-creation of folder/suite hierarchy, auto-creation of missing tags, safe defaults for status and priority, and the return value including shareUrl. This gives an agent a solid mental model of side effects without contradicting the 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 dense but not bloated; each sentence contributes a useful rule or scenario, and the 'IMPORTANT' note about omitting status and priority is front-loaded. It earns its length for a complex creation tool.

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 tool with 13 parameters, no output schema, and no meaningful annotation signals, the description covers the key mental model: where cases must live, how folderId vs projectId resolve, auto-creation behavior, tag defaults, and return shape. Minor wrinkles like precedence when both folderId and projectId are passed are not necessary for the agent to correctly invoke the tool in common cases.

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 schema already documents 100% of parameters with detailed descriptions, defaults, and auto-creation semantics. The description restates the A/B targeting choices and default behavior at a high level, but adds only marginal parameter insight beyond the 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 clearly states the specific verb 'Create' and resource 'test case in a test suite', then firmly distinguishes the tool's scope with 'Test cases MUST live inside a suite (not a bare folder)'. This removes ambiguity against sibling tools like create_suite or create_folder.

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?

It gives explicit when-to-use guidance by defining two valid targeting paths: folderId or projectId with optional folderName/suiteName, including auto-creation behavior. It does not explicitly name sibling alternatives like update_test_case, so it falls just short of full alternative routing.

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