tickets_create_case

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

With no annotations provided, the description carries the full burden, and it delivers: it discloses that this is a write operation, reaches the real SOC, creates a genuine support case, and warns that invalid combinations are rejected. This is exactly the high-impact behavioral information an agent needs before invoking a mutating tool.

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?

Four short, purposeful sentences. The most critical fact ('WRITE -- reaches the real SOC') is front-loaded, followed by the human-confirmation warning and the validation prerequisite. Every sentence earns its place, and there is no redundant or filler content.

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 15-parameter schema with 100% coverage and an output schema present, the description covers the remaining non-obvious context: real-world impact, need for human confirmation, and the requirement to validate against tickets_case_type_configs first. An agent has everything necessary to decide whether and how to call this tool correctly.

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 the baseline is 3. The description adds some semantic guidance by naming case_type, case_subtype, and service in the validation instruction, but it does not add new meaning or formatting details beyond what the schema already documents. It is sufficient but not exceptional.

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?

Description states the exact operation: 'Create a new case in eSentire's ticketing system.' It is clearly a create action, which distinguishes it from sibling tools like tickets_update_case or tickets_list_cases. The parenthetical 'WRITE -- reaches the real SOC' reinforces the resource and impact without ambiguity.

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 gives explicit usage context: confirm intent with a human before calling, and validate case_type/case_subtype/service against tickets_case_type_configs first. It does not explicitly name alternatives or state when not to use it beyond the human-confirmation caveat, but the 'create new' framing plus the validation instruction is strong practical guidance.

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