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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond annotations: the MCP panel renders an interactive map with selectable spots and cameras, coordinates are not safe navigation routes, units are specified, and it returns source/freshness metadata. This is solid additional behavioral disclosure.

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 front-loaded with the core purpose and return fields, then moves to usage, parameters, and caveats. It is slightly dense but each sentence contributes relevant information; no major redundancy or wasted space.

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?

For a list tool with no output schema and nested parameters, the description provides sufficient context: what is returned (fields, metadata), units, map rendering behavior, and downstream usage. The main gap is the absence of explanation for the region and homeZone parameters, but overall it gives an agent enough to invoke the tool 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 description coverage is reported as 0%, so the description should compensate. It only explains the 'include=status' parameter; the 'region' and 'homeZone' parameters are not mentioned at all. While region enum values are self-explanatory, homeZone is ambiguous, and the description fails to clarify these filtering options.

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 states a specific verb and resource ('Every named South Florida spot the app scores') and enumerates returned fields (lat/lon, kind, region, NOAA stations). It implicitly distinguishes from get_spot (single spot) and find_* (filtered by type) by emphasizing 'every named spot' and its use for a comprehensive map.

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 provides clear use cases: 'Use this for a map of verified coastal spots' and 'Use the returned id with conditions, forecast, tides, hazards and briefing tools.' It also explains that include=status adds current-hour scores. However, it does not explicitly name alternative tools like find_beaches or find_inlets, leaving some inference required.

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