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

The annotations already establish that this is a read-only, open-world, idempotent, non-destructive operation. The description adds meaningful behavior context beyond that: the data comes from anonymous reports, is limited to roughly the last 3 hours, and is currently concentrated in Tampa Bay.

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 a single front-loaded sentence that immediately states the resource and then lists relevant condition types. It is appropriately compact, though the long list and parenthetical caveat make it slightly dense.

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 simple one-parameter schema and rich annotations, the description covers the key missing context: source, recency, coverage limits, and the kinds of information returned. It does not describe behavior when no recent reports exist, but it is otherwise complete for this tool.

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 description coverage is 100%, and the single place parameter is already documented as a place name or place_id from find_places or boat_ramps. The description reinforces that the place is a pier or boat ramp, but it adds little syntax or selection guidance beyond 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?

The description clearly identifies the resource as current conditions at a pier or boat ramp and lists the specific condition types reported. It implies differentiation from forecast or official-data siblings through its emphasis on live anonymous reports from the last 3 hours, but it does not explicitly name alternatives.

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?

It gives clear usage context: use for what conditions are like right now, based on reports from the last 3 hours. It also includes a useful coverage caveat that reports are mostly from Tampa Bay so far, though it does not state when not to use it or name sibling alternatives.

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