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

Annotations only cover the safe-read profile (readOnly/idempotent/non-destructive), so the description carries the real burden and does so richly: alcohol is 'a sentence to quote, not a boolean', glassBottles holds even where alcohol is allowed, fireOrGrill/dogs are per-spot, closesAt is computed from that spot's coordinates, and hoursText means the line wasn't machine-readable. This is exactly the beyond-annotations context an agent needs.

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?

Dense but front-loaded: legal-rule framing, then the alcohol trap, then field semantics, then hours caveat, then the beach_info exclusion. Most sentences earn their place, though the summons aside and the enumerated venue types are slightly more color than strictly needed.

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?

No output schema exists, so the description must explain returns, and it does: 'Returns up to 8' plus semantics for alcohol, glassBottles, fireOrGrill, dogs, closesAt, and hoursText. Combined with the annotation-covered safety profile and the explicit sibling boundary, an agent has everything needed to call and interpret this 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 coverage is 100%, so baseline is 3, but the description adds genuine meaning: it clarifies that `allows` accepts the picnic's needs and that filtering on 'alcohol' includes wine-only and permit-only spots each flagged in their own line. It less directly elaborates `town`/`query` beyond the schema wording, so it slightly exceeds rather than fully transcends the schema.

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?

Opens with a concrete verb+resource+scope ('Verified East End picnic grounds') and immediately names distinctions from siblings ('The guide holds NO drinking rule for the ocean beaches — those are beach_info's'). An agent can separate this from beach_info, search_places, and things_to_do 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?

Explicit triggering conditions ('Call this for any picnic, blanket, park, park-hours, barbecue or fire-pit question') and a hard rule ('ALWAYS before saying anyone can drink outdoors'), plus a clear exclusion and routing to the alternative ('never infer one from these'). Nothing is left to inference.

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