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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context by naming the concrete fields returned and the underlying endpoint, but discloses nothing about auth requirements, rate limits, or what happens when no tier exists.

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 compact sentences that front-load the returned fields before the endpoint reference. Slightly less than ideal because the raw API path adds little actionable value for an agent.

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 single-parameter read tool with no output schema, the description helpfully enumerates the returned capacity fields while annotations cover the safety profile. It is nearly complete, missing only guidance on how to locate event_id or handle an absent capacity tier.

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% with a single event_id parameter documented as 'Event ID.', so the schema already carries the parameter semantics. The description adds no format or constraint detail beyond what the schema provides, making the baseline of 3 appropriate.

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 (Fetch) and resource (event capacity tier), then enumerates the exact data returned (capacity_total, capacity_sold, capacity_pending, quantity_total, holds). This is clearly distinguishable from sibling read tools like eventbrite_get_sales_report or eventbrite_list_inventory_tiers.

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?

Usage is only implied through the name and the enumerated fields; there is no statement of when to use this versus eventbrite_list_inventory_tiers or eventbrite_get_event, and no prerequisites or exclusions are given.

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