create_ticket

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. The only fact offered — that the ticket is stored with status open — largely restates the verb 'Open' and says nothing about side effects such as whether the requester is notified, whether duplicates are rejected, or whether the call is idempotent.

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?

Two short, front-loaded sentences with no padding. The second sentence partially restates what 'Open a new ticket' already implies, so it is efficient but not entirely waste-free.

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?

An output schema exists and every parameter is documented in the schema, so return values and inputs are covered elsewhere. What is missing is context an agent would want for a mutation with no annotations: whether creating a ticket triggers notifications or requires a duplicate check.

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 100%, including the conditional access_token requirement and the meaning of each field, so the schema already does the heavy lifting. The description adds no meaning beyond it, which is the baseline 3 case.

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 states a specific verb and resource ('Open a new ticket'), which clearly marks this as the creation tool and separates it from list_open_tickets, get_ticket, search_docs, and get_doc. It does not explicitly name or contrast with any sibling, which keeps it just short of a 5.

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?

There is no guidance on when to create a ticket versus searching existing ones or reading a ticket first, and no mention of prerequisites such as duplicate checks or required requester context. The usage is only inferable from the verb itself.

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