create_test_case

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

No annotations are provided, so the description carries the full burden. It only states that a test case is created, without disclosing behaviors such as duplicate name handling (block, generate_new, create_new_version), whether it validates existence of parent entities, or what the response contains. For a mutation tool, this is insufficient.

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 a single, front-loaded sentence with no fluff. It immediately states the action and resource. However, it is so brief that it sacrifices necessary context, which slightly reduces the effectiveness of its conciseness.

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?

This tool has 12 parameters and no annotations or output schema. The one-sentence description is far too minimal to guide an agent on required inputs, optional behaviors, or expected results. It leaves significant gaps in how to invoke the tool correctly.

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?

Schema description coverage is only 25%, and the description adds no parameter-specific meaning beyond mentioning 'test suite'. The schema itself does describe a few fields (authorLogin, executionType, actionOnDuplicatedName), but the description fails to compensate for the low coverage, leaving many parameters undocumented.

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 action ('Create') and the resource ('a new test case'), and specifies the context ('inside a test suite'). This distinguishes it from sibling tools like create_test_suite or update_test_case, so the primary purpose is unambiguous.

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 implies when to use this tool (to add a test case to a suite) but provides no explicit exclusions or alternatives. It doesn't mention prerequisites like needing a valid testProjectId or testSuiteId, nor does it contrast with create_test_suite. The context is understood but not elaborated.

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