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

The description adds behavioral context beyond annotations by emphasizing anonymity and aggregation: 'anonymous aggregate', 'No user identity is returned'. This informs the agent that results are anonymized and observational, consistent with the readOnlyHint and destructiveHint annotations. It does not contradict annotations.

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 extremely concise at two sentences, front-loading the core action and key constraints. No superfluous information; every phrase adds value.

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 output schema exists, the description need not detail return values. It covers the tool's purpose, anonymity, and scope. For a simple tool with two parameters, the description is largely complete, though it could mention that the aggregate is limited to active reports (already stated).

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?

The input schema has 0% schema description coverage, but the description only indirectly references spotId ('for one spot') and does not explain the lang parameter (e.g., its purpose as locale) or the uuid format. With low coverage, the description fails to compensate by clarifying parameter semantics or constraints.

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 states it retrieves an anonymous aggregate of active BeachFinder community reports for one spot, specifying the verb 'Get', the resource 'community reports', and the scope 'for one spot'. This distinguishes it from sibling tools like get_spot_conditions (likely official) and get_spot_details (general details).

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?

The description implies usage for obtaining community reports but does not explicitly state when to use this tool versus alternatives like get_spot_conditions or get_spot_details. No 'when not to use' or recommendation for other tools is provided.

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