add_test_case_step

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

No annotations are provided, so the description carries the disclosure burden alone. It does add genuine context beyond the schema: the mutual-exclusivity rule, the parent/child nesting effect, and the returned identifiers. However, it says nothing about where the new step is placed in the ordering, what permissions or preconditions are required, or what happens on failure. For a mutation tool with zero annotation coverage, these are meaningful gaps.

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 purpose is front-loaded in the first clause, followed by the return shape and two tight constraint lines. Every sentence adds distinct information and there is no redundant restatement 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?

An output schema exists, so the description needn't explain return values, though it helpfully names the returned fields anyway. For a five-parameter mutation tool with no annotations and no schema descriptions, the definition covers purpose and parameter roles but omits ordering/position semantics, permission requirements, and error behavior. It is adequate but not complete.

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 0%, so the description must compensate, and it largely does: it defines body as step text, groups attachment_id and shared_step_id as the alternate step sources, and explains that parent_step_id creates a child step. test_case_id is implicitly grounded by 'add a step to a test case scenario.' It does not clarify what an attachment_id or shared_step_id actually references, leaving one gap in an otherwise strong pass.

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 states a specific verb and resource: 'Add a step to a test case scenario.' That distinguishes it clearly from siblings like create_test_case, get_test_case_steps, and update_test_case. It doesn't explicitly name those siblings, but the action and target are unambiguous enough that no reasonable confusion exists.

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 real usage context by declaring that exactly one of body, attachment_id, or shared_step_id must be supplied, and that parent_step_id nests the new step under an existing one. That tells the agent how to choose between the three step-creation modes. It stops short of naming alternatives or when-not-to-use conditions, so it is clear context without exclusions.

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