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

Annotations already declare readOnly/idempotent/closed-world, yet the description still adds substantial behavioral context: results cap at 10, `townScope` reports how the place argument was read, unrecognized towns yield an empty rows array plus `didYouMean`, and ticket-rate fields carry provenance about who published them. The `publishedRate` false/true semantics and the warning that `tickets.tier` is a relative band rather than a figure are exactly the kind of disclosure an agent needs to avoid misreading results.

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 resource and scope are front-loaded, and nearly every clause carries a distinct fact about a returned field rather than restating the name. It is dense and run-on in places, packing many field-level claims into one paragraph, but little is genuinely redundant given there is no output schema to carry them.

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?

With no output schema and five optional filters, the description does the heavy lifting: it describes the returned record's structure (`tickets.published`, `publishedTiers`, `beneficiary` with donateUrl/volunteerUrl, `alsoThisSeason`), the 10-row cap, and the empty-result path. An agent could call this correctly and interpret the response without further documentation.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains how the `town` argument is interpreted (via `townScope`, with near-match fallback) and that `from` reaching into the past is the only way to surface held benefits. It doesn't add syntax detail for `query` or `cause` beyond what the schema already says, which keeps it from a 5.

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 names a specific resource and scope: 'The East End's 2026 benefit season: 15 dated charity galas, each joined to the nonprofit it raises for.' That is concrete enough to separate it from generic siblings like upcoming_events or things_to_do, and the closing note about past benefits makes the temporal boundary explicit.

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 implied rather than stated up front: past events appear only when `from` is an earlier date and `townScope.recognized: false` explains empty results. But the description never plainly says when to pick this over upcoming_events or things_to_do, nor does it state the intent ('charity galas' vs general events) as a selection rule; the when-to-use conditions live mostly in the schema text.

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