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

With no annotations, the description carries the full burden. It discloses that the tool works offline, which is a useful behavioral trait, but it omits crucial details: expected coordinate format, output structure, error handling, or any limitations. The description is too sparse to provide meaningful transparency about how the tool behaves beyond its offline nature.

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 extremely brief, but that brevity comes at the cost of clarity. It is more of a tagline than a functional description. While it is front-loaded with the core idea, it lacks necessary detail, making it under-specified rather than appropriately concise.

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 tool's simple nature, the description still leaves out essential information. The input parameter format is undocumented, and there is no mention of the output (though an output schema exists, it is not visible here). An agent cannot reliably call this tool without guessing the input format. The offline hint is the only contextual detail provided.

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?

There is a single parameter 'q' with no schema description (0% coverage). The description does not mention the parameter at all, so it adds no meaning beyond the raw schema. An agent has no idea what format 'q' should take (e.g., 'lat,lon' or a string like '40.7,-74.0'). This is a critical gap.

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 states a clear purpose: compute the opposite point on Earth for given coordinates. It is specific enough to distinguish from general geocoding tools like geocode or revgeo, though it does not explicitly contrast with them. The verb 'opposite point' is clear, and the resource (Earth coordinates) is defined.

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 guidance on when to use this tool versus alternatives like geocode, latlonformat, or revgeo. The only hint is '(offline)', which implies it works without network access, but no explicit conditions or exclusions are given. An agent would not know whether to choose this over a similar tool without additional context.

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