Run raw Overpass QL

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that data is full-planet OSM 'minutes behind live,' that queries default to 25 seconds without [timeout:], and where to learn syntax and server differences. These details materially shape safe invocation.

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?

Four dense sentences carry high-value information with no filler. The most identifying action is front-loaded, followed by routing guidance and then concrete query construction rules.

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 one parameter, read-only semantics, and no output schema, the description covers what an agent needs to call the tool successfully: how to format the query, what the timeout behavior is, and pointers to authoritative references for syntax and server-specific differences.

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 single query parameter is already fully described in the schema with an example. The description adds extra meaning by emphasizing output caps, area bounding, and the [out:json] convention, which helps the agent construct valid queries rather than just knowing the parameter type.

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 and resource: 'Run a raw Overpass QL query against the Overspan hosted Overpass API.' It also distinguishes itself from the sibling helpers by saying to use it when 'the helper tools are too narrow,' making the tool's role clear.

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 gives explicit when-to-use guidance ('Use this when the helper tools are too narrow') and concrete procedural requirements: bound the query to an area, cap output, start with [out:json], and be aware of the 25-second timeout default. This is unusually actionable.

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