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

With only destructiveHint=true in annotations, the description carries substantial extra weight: it warns that this creates a real ticket that consumes release capacity and that the only undo is voiding it in the Tito dashboard. That is exactly the consequence framing an agent needs before invoking an irreversible mutation.

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?

Three tight sentences with the purpose and its non-obvious consequence front-loaded; the trailing API endpoint line is mildly extraneous but cheap and informative. Nothing is padded.

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 create tool with 11 parameters, no output schema, and a nested metadata object, the description covers outcome, side effect on capacity, and reversal path. The remaining gap is what registration/ticket data comes back, which is a minor omission given the schema is fully documented.

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 naming of required release_id and event_slug, so the schema already explains every parameter. The description adds scoping context (issuing from a release) but no field-level syntax or defaults, so the baseline 3 applies.

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?

States a specific verb (issue) and resource (ticket) with the precise distinction that matters: it creates a manual registration without a checkout. That contrast with the normal purchase flow, plus the named use cases (speaker, sponsor, comp), makes it unmistakable against siblings like tito_create_discount_code or tito_get_ticket.

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?

Gives clear positive context ('without a checkout — e.g. a speaker, sponsor or comp ticket'), which tells the agent when this tool is appropriate. It stops short of naming alternatives or exclusions (e.g. directing normal paid purchases elsewhere), so it is clear but not fully routing.

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