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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral context well beyond them: enforcement.enforcedRightNow is computed from season and daily window against local clock, off-season/after-6pm changes the answer entirely, and 16 beaches are flagged outsideTheStickerMap. It even pre-empts the commonest wrong answer (East Hampton Town sticker vs Main Beach).

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?

Front-loaded with the core purpose and the parameter contract, and nearly every sentence adds a distinct fact (permit grants, explicit non-grants, day passes with prices, fine, enforcement clock, outside-the-map flag). It runs long for a one-parameter tool and carries a few rhetorical flourishes that could be trimmed.

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?

There is no output schema, so the description carries the full burden of describing the return payload — and it does: granting permits, explicit non-grants, non-resident/day-pass options with prices, the fine, where to apply, the enforcement boolean, and the outsideTheStickerMap flag. An agent knows what it will get back before calling.

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% with a single optional param, so baseline is 3; the description goes further by explaining the semantic consequence of each accepted form (specific lot verdict, jurisdiction-plus-beach-lines, or full map) and by noting that a town/village/hamlet is a valid value, not just a beach name. It does not add format or matching rules beyond the example list.

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: resolves East End beach-parking permit rules across all 7 jurisdictions against the beach or town asked about. It explicitly distinguishes itself from the sibling beach_info, which handles dogs, lifeguards and car-free access, so an agent can route between them without opening either 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?

Gives the exact three input modes — a beach name for a lot verdict, a town/hamlet for that jurisdiction plus its beaches' permit lines, and omission for the whole map — and names the alternative tool for adjacent questions. It also states the interpretive payoff ('yes, you can just park') for state/county/DEC beaches, which is when-not-to-worry guidance.

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