add_case

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

Annotations already indicate the tool is not read-only, not destructive, and not idempotent. The description adds some behavioral context by warning that using unknown field names results in an error, but it does not elaborate on other behaviors such as whether the operation can be undone or if it triggers side effects.

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 extremely concise with only two sentences, both front-loaded with essential information. Every word serves a purpose without redundancy or unnecessary detail.

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 absence of an output schema, the description does not explain what the tool returns (e.g., the created case object). However, it covers the key prerequisite and error condition, making it adequate for a creation tool. Including the return value would improve completeness.

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?

The input schema has full description coverage (100%). The description for the 'fields' parameter goes beyond the schema by explaining how the server merges entries directly into the request body and providing an example, which adds significant clarity beyond what the schema provides.

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 tool creates a new test case in TestRail, with a specific verb ('Create') and resource ('test case'). It distinguishes itself from sibling tools like 'update_case' and 'get_cases' through the creation action.

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 a clear usage prerequisite: knowing valid field names from 'get_case_fields'. It implies when to use this tool (when creating a case) but doesn't explicitly state when not to use or mention alternatives, though sibling tools are available for other operations.

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