append_test_steps

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the 'max 100 steps per request' constraint, which is useful. However, it doesn't address critical behaviors: whether this is idempotent, what permissions are required, how it handles duplicate steps, error conditions (e.g., invalid testCaseKey), or what the response looks like (success/failure indicators). For a mutation tool with zero annotation coverage, this leaves significant 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 description is a single, efficient sentence with zero waste. It's front-loaded with the core purpose and includes a key constraint. Every word earns its place, making it easy for an agent to parse quickly.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., idempotency, error handling), response format, and usage context relative to siblings. While concise, it doesn't provide enough context for reliable agent invocation in complex scenarios.

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%, so the schema fully documents both parameters (testCaseKey format, steps structure with nested properties). The description adds minimal value beyond the schema—it reiterates the 'max 100 steps' limit already in the schema's maxItems, but doesn't provide additional context like example usage or edge cases. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Append new test steps') and resource ('to a test case'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'update_test_case' or 'create_test_case' that might also modify test cases, leaving some ambiguity about when this specific append operation is preferred.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., test case must exist), exclusions (e.g., cannot append to archived cases), or comparisons to sibling tools like 'update_test_case' or 'get_test_steps'. The agent must infer usage from the name alone.

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