bbox-mcp-server

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

With no annotations provided, the description carries the full burden but omits key behavioral details: it does not describe the output format (e.g., whether it returns hex IDs with counts, GeoJSON, or raw data), pagination behavior, or rate limiting concerns typical of Overpass queries.

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 single sentence is tightly constructed with zero redundancy, front-loading the core action and progressing logically through processing method and purpose. Every clause provides essential context.

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 absence of annotations and output schema, the description adequately covers the input purpose but remains incomplete regarding return value structure and behavioral constraints. For a tool requiring domain knowledge (Overpass QL, H3), additional context on output format would improve utility.

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%, establishing a baseline of 3. The description reinforces the 'resolution' and 'query' parameters but does not add semantic value beyond the schema regarding the mutual exclusivity of 'location' vs 'bbox' or syntax guidance for Overpass QL.

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 specific action (executes Overpass query), processing method (bins into H3 hexagons), and analytical purpose (spatial density analysis). It implicitly distinguishes from sibling `search_overpass` by emphasizing aggregation/binning versus raw retrieval.

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 'to analyze spatial density' implies the use case, but the description lacks explicit guidance on when to choose this over `search_overpass` (raw data) or `get_h3_indices` (pure hex generation), and does not mention prerequisites like Overpass QL knowledge.

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