create_case

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

No annotations are present, and the description merely restates the action implied by the tool name. It does not disclose side effects, permission requirements, validation behavior, or how missing optional parameters like region are handled.

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?

While the description is short, it is under-specified for a tool with four parameters and a nested fields object. Its brevity results in a lack of useful content, so it is not appropriately sized.

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 creation tool with nested objects and an output schema, a one-sentence description is severely inadequate. It does not explain the relationship to domains, templates, or fields, nor does it clarify defaults or expected behavior.

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%, and the description provides zero information about the four parameters (domain_id, template_id, fields, region). It does not compensate for the absent schema descriptions, leaving the agent without guidance on required inputs.

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 'Create a new case' uses a specific verb and resource, clearly distinguishing it from sibling tools like get_case, search_cases, and cases_update_case. It unambiguously identifies the tool's core purpose.

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?

No guidance is provided on when to use this tool versus alternatives such as cases_create_template or cases_create_related_item. There is no mention of prerequisites, typical scenarios, or exclusions.

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