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

With no annotations, the description carries the full burden of behavioral disclosure, and it is remarkably forthcoming about quirks: dead ticket links, unpublished rates, the need to quote verbatim from `publishedTiers`, and the 'from' parameter gating past events. However, a few numerical inconsistencies (e.g., 'Cocktail' on 16 of 15 events, 'wrong twenty-six times out of twenty-seven') introduce confusion in an otherwise transparent account.

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?

The description is densely packed with essential caveats, but it is also overlong and at times convoluted (e.g., 'unknowable from your weights', 'cuts both ways', 'the black-tie assumption you would reach for is wrong twenty-six times out of twenty-seven'). While front-loaded with purpose and usage, several sentences could be tightened without losing meaning, and the internal contradictions undermine clarity.

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?

Given the tool's complex data model (ticket pricing nuances, dress codes, beneficiary info, seasonal fixtures) and the absence of an output schema, the description is remarkably complete. It tells the agent what fields exist, what to quote, what to avoid estimating, how to handle donation/volunteer questions, and how to interpret edge cases like dead links and unpublished rates.

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?

Although the schema already covers all five parameters, the description adds substantial semantic value beyond the field names: it explains the meaning of `tickets.publishedRate`, `tickets.tier`, `tickets.publishedTiers`, `beneficiary`, and `alsoThisSeason`, and it operationalizes the `from` parameter ('Past benefits never appear unless you pass `from`'). This goes far beyond the schema's minimal descriptions.

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?

The description clearly identifies the tool's domain: '15 dated charity galas, each joined to the nonprofit it raises for.' It goes beyond the title by explicitly enumerating the question types it answers ('gala, benefit, fundraiser, charity, black-tie, what-should-I-wear, where-can-I-donate or where-can-I-volunteer'), making it easy to distinguish from sibling tools like `upcoming_events` or `community_help`.

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 explicit, actionable guidance on exactly when to invoke the tool: 'Call this for any gala, benefit, fundraiser, charity, black-tie, what-should-I-wear, where-can-I-donate or where-can-I-volunteer question.' It also provides strong negative guidance, e.g., 'NEVER state or estimate a price' when `tickets.publishedRate` is false, and explains the `from` parameter's role for accessing past benefits.

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