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

Beyond readOnly/idempotent annotations, it discloses the upstream system (Mote Marine), update cadence (~twice a day), the ~131-beach coverage footprint, and a crucial safety caveat that it 'never says the water is safe.' It does not say what happens for a location outside coverage, which would complete the picture.

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-loads the flag meaning, but it is one dense run-on paragraph that packs parenthetical flag definitions, a beach list, water-quality notes, and a volunteer-recruitment line together. The Ambassador volunteering sentence is useful for output framing but competes for attention with the core purpose.

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, the description carries the return shape and does so (flag meaning, speakable sentence, volunteer info, safety disclaimer). Coverage and freshness are covered; only out-of-coverage/empty-result behavior is unaddressed.

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 real semantics by framing lat/lon and place as alternative input modes ('Give a position or a beach/town name'), which the flat schema does not express. It also implies the latitude/longitude pair is a location anchor rather than an independent filter.

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 resource (the daily lifeguard-reported warning flag at nearby beaches) and its source, cadence and geography. An agent can immediately tell this apart from siblings like beach_water, red_tide or live_conditions because the description enumerates the flag vocabulary and the report contents.

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 only: 'Give a position or a beach/town name' tells the agent how to invoke but not when to prefer this over beach_water or red_tide, which are adjacent safety/water tools. No exclusions or alternatives are named.

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