mutate_suite

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

Annotations already indicate this is a mutation (readOnlyHint=false), and the description adds the dual create/update mode controlled by 'payload.action'. It doesn't disclose additional behavioral details like whether updates are partial, permissions required, or side effects. Given the annotations cover some safety profile, a score of 3 is appropriate.

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 that clearly states the purpose and the key usage instruction. Every word earns its place; it is concise without being under-specified.

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 the tool's complexity (one parameter with two possible shapes), the description covers the essential context: what the tool does and how to select create vs. update. The schema enriches the details. However, it does not mention potential return values or side effects, though the annotations provide some behavioral context. Slightly more detail could be added, but it is largely 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 coverage is 100%, so all parameter descriptions are already present in the schema. The description only restates the 'action' values ('create' or 'update') which are already defined as consts in the schema. It adds no new semantic meaning beyond what the schema provides, matching the baseline of 3.

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 uses a specific verb and resource: 'Create a new test suite or update an existing one in TestRail.' This clearly states the tool's function and distinguishes it from sibling tools like mutate_section or mutate_run. The mention of 'create' or 'update' operations further pins down the exact behavior.

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 clearly implies when to use the tool: when you need to create or update a test suite. It specifies the operation via the 'action' field, giving concrete usage context. However, it does not explicitly mention alternatives or when not to use this tool, so it falls short of a 5.

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