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

Annotations provide only destructiveHint=true, so the description carries the real behavioral load and does it well: it discloses that the event is not visible or on sale until a separate publish call, and that ticket classes must be attached before publishing. It omits auth/permission expectations and whether the draft can be deleted or is permanent.

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 short sentences, zero filler: the lifecycle constraint is front-loaded, then the ordering requirement, then the API endpoint. Every sentence earns its place.

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 20-parameter mutation with no output schema, the description covers the essential unknown (draft lifecycle and required follow-up calls) and the schema covers field-level detail. Missing only failure/auth expectations and what the response returns (event ID for subsequent ticket calls).

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 20 parameters (including mutually exclusive constraints like listed vs invite_only and venue_id vs online_event), so the schema does the heavy lifting. The description adds no per-parameter meaning beyond the sequencing note about ticket classes; 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+resource+state: 'Create a new event as a DRAFT'. The parenthetical explains exactly what the draft state means and names the sibling (eventbrite_publish_event) that changes it, so an agent can distinguish this from publish/unpublish/update_event at a glance.

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 sequencing guidance: create as draft, then add tickets via eventbrite_create_ticket_class, then publish via eventbrite_publish_event. It names the follow-on alternatives and their order, but does not state when a different creation path (e.g., eventbrite_copy_event) would be preferable.

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