get_nearby_hotspots

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the main behavior (find hotspots near coordinates) and implies a read-only search, but it does not mention result limits, sorting, default radius, or whether only currently active hotspots are included. The schema supplies some parameter semantics, but the description itself adds minimal behavioral context beyond the core action.

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 sentence that front-loads the primary action and resource, then adds a practical use case. Every word earns its place; there is no fluff or repetition of schema details. It is appropriately sized for the tool's simplicity.

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 geospatial search tool, the description provides enough context for agent selection and invocation: it states the input (latitude/longitude) and the user need. The schema covers all parameters, and no output schema exists, but a list-returning search tool is adequately described by 'find hotspots'. It could mention output format or distance defaults, but these are implied or captured in the schema.

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% for all four parameters, so the baseline is 3 even though the description does not mention parameters. The description adds no semantic value to the schema's already clear parameter descriptions for lat, lng, back, and dist. The coordinate context is implicit in the description, but the schema already defines each parameter.

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 opens with a specific verb 'Find' and resource 'birding hotspots' near a latitude/longitude. This clearly distinguishes it from the region-based sibling 'get_hotspots_in_region' and from 'get_hotspot_info' which targets a specific hotspot. The quoted use case 'where should I bird near here' reinforces the tool's intent.

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 phrase 'near a latitude/longitude' together with 'perfect for' gives clear context for when to use this tool: coordinate-based proximity searches. It does not explicitly mention alternatives or exclusions, but the coordinate scoping effectively separates it from region-based tools. No misleading guidance is present.

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