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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real behavioral context: module steps are included and appended after test_steps, and critically that 'the Module itself is unchanged' — a non-obvious side-effect clarification the annotations do not convey. It stops short of disclosing what is returned or any permission requirements.

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?

Two tightly written sentences, front-loaded with the create semantics before the routing hint. No filler and no repetition of the tool name.

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 13-parameter mutation tool with no output schema, the description covers create semantics and the bulk alternative but says nothing about the response (e.g., the created case's id) which the agent will need for follow-up calls. Folder placement when folder_id is omitted and the project-default status behavior are left entirely to the schema.

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 100% and the schema already documents all 13 parameters, including the module append-order note and the 'outcome' key constraint. The description adds almost nothing beyond the schema, so the baseline 3 is appropriate.

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?

States a precise verb (Create), resource (a single test case), and scope (in a project folder, with optional steps and module references), and explicitly contrasts itself with the bulk sibling tm_generate_test_cases. An agent can route between the two without opening either schema.

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 names the condition that selects the alternative: 'For creating many cases from a requirement, prefer tm_generate_test_cases.' That is a clear when-to-use-this vs. when-to-use-something-else statement, plus an implicit boundary (single vs. many).

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