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

With no output schema and only safety annotations, the description carries real behavioral load and delivers: secret:true hides the tier and returns an auto-generated secretCode (SECRET_XXXX), and paid tiers can be added before Stripe is connected with the host's share held until connection (community-routed events sell only after payouts are set up). These are non-obvious side effects an agent must know.

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?

Front-loads the core action, then appends the secret-code and Stripe/payout behaviors in a single dense paragraph. Every clause carries information, though the run-on structure around the promo-code and Stripe clauses reduces scannability slightly.

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 8 parameters and no output schema, the description covers the key behaviors, including the secretCode return and Stripe/payout timing, which is what an agent needs. It stops short of documenting a few params (max_per_person, description), but the overall picture is sufficient to invoke 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 description coverage is 0%, so the description must compensate for 8 parameters. It explains secret (unlock code), price (0 = free RSVP), capacity, requires_approval, and event_id, but says nothing about name, description, or max_per_person, leaving a meaningful gap.

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 ("Add a ticket tier to a live event you manage") and immediately distinguishes the two variants (free RSVP at price 0 vs paid) with capacity and optional approval. An agent can separate this from siblings like update_ticket_tier, delete_ticket_tier, and reorder_ticket_tiers without opening any schema.

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?

Provides clear prerequisites ("Requires event_id; you must be a host") and routes to an alternative for a related task: "for your own code, create_promo_code with applicable_classes [ticketTierId]." It does not explicitly contrast add vs update/archive, but the create semantics plus the named alternative give strong context.

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