tickets_create

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

No annotations are provided. The description adds a behavioral note that line_items cannot be added inline, which is beyond the schema. However, it does not disclose other behaviors like return value, permissions, or 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, each carrying important information. No unnecessary words, and the critical note is placed at the end.

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?

The description lacks information about the output/return value, which would be helpful for an 18-parameter tool with no output schema. It also does not mention how to retrieve the created ticket ID, leaving some gap.

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% with all parameters described. The description does not add additional parameter-specific meaning beyond the schema, so a baseline score of 3 is appropriate.

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 'Create a new ticket' with a specific verb and resource, and distinguishes from sibling tools by noting the line_items limitation, which is a key differentiator.

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 explicitly states when to use the tool (to create a ticket) and provides a clear alternative (tickets_add_line_item) for adding line items after creation. It does not cover all edge cases but is helpful.

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