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

No annotations are provided, so the description carries the full behavioral burden. It discloses the breadth of the operation (multi-source aggregation of address, sun, POI, and link data), which is useful, but says nothing about rate limits, external dependencies, caching, or whether the call is purely read-only. The lack of annotations keeps this from being higher.

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?

A single dense line with the core concept front-loaded and zero filler. Its compact arrow notation efficiently conveys input-to-output flow, though it is terse enough that some readers may want slightly more.

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?

An output schema exists, so return values need not be described, and the description appropriately focuses on the aggregation scope. However, with no annotations and an undocumented solo parameter, the definition leaves input format and behavioral context under-specified for an agent to call it confidently.

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 0% and the single parameter 'q' has no description, so the schema alone tells the agent almost nothing. The description's 'Coords/place' prefix does communicate that q accepts either coordinates or a place name, which is real added meaning, but no coordinate format or example is given.

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 names the resource (GPS context) and enumerates the concrete outputs it aggregates: address, sun times, nearby POIs, map links. It is clearly distinguishable from single-purpose siblings like geocode or suntimes by positioning itself as a 'Full Context' bundle. It does not name siblings explicitly, so it stops short of a 5.

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 statement of when to use this versus alternatives such as geocode, revgeocode, suntimes, or whatsnearby. The 'Full Context' framing hints that it is a one-shot aggregator, but the agent must infer that; no exclusions or conditions are given.

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