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

Annotations only supply destructiveHint=true, but the description adds substantial behavioral context beyond them: the ticket counts against the release's capacity and can only be undone by voiding it in the Tito dashboard, i.e. it is not removable via API. It also discloses the underlying endpoint (POST /:account/:event/tickets), reinforcing that this is a real write operation.

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 sentences, front-loaded with the purpose and followed by the capacity/irreversibility warning. 'Tito creates a manual registration for it' slightly restates the opening sentence and the raw endpoint line is of marginal value, but there is no real bloat.

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 mutation tool with thin annotations and no output schema, the description covers the key risk (capacity consumption, void-only undo). It does not say what the response contains or how to locate the created ticket later in order to void it, which is a modest gap given there is no output schema to fall back on.

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% across all 11 parameters, with release_id and account_slug already documented including slug/numeric-id forms and the TITO_ACCOUNT fallback. The description adds no parameter-level detail, 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 and resource ('Issue a ticket for a release') and immediately scopes it as issuance without a checkout, with concrete examples (speaker, sponsor, comp). This distinguishes it cleanly from siblings like tito_create_discount_code, tito_update_ticket, and the various list/get tools.

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 clear context for when this tool applies ('without a checkout — e.g. a speaker, sponsor or comp ticket'), which is exactly the scenario an agent needs. It does not, however, state exclusions or name an alternative path for normal checkout-based issuance, so it stops short of full when/when-not guidance.

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