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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context: the data source is user-submitted field reports, the window is fixed at the last 120 days, and the content spans specific categories. However, it does not disclose pagination, rate limits, or the return format.

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 with no filler. The colon-separated list of report types is somewhat long but directly informs the agent about the data's content, so it earns its place.

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 simple read-only tool with a fully documented schema and annotations, the description covers the data source, time window, and content categories. Yet with no output schema, it should describe the return structure (e.g., a list of reports with fields) and any pagination or result limits, which it does not.

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 lat, lng, and radius_km are fully documented in the schema. The description adds the implicit meaning that the radius parameter drives the search and that results are always limited to the last 120 days, but it provides no additional syntax or format details 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 states the resource (field reports from map users), the spatial scope (within a radius), and the temporal scope (last 120 days). It enumerates the kinds of conditions reported, which helps distinguish it from a submission tool like report_conditions, though it does not explicitly name that sibling.

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?

There is no explicit guidance on when to use this tool versus alternatives such as report_conditions, find_spots, or camp_map_pass. The description implies usage by describing the returned data, but it offers no conditions for selection or exclusions.

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