geo

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, yet it says nothing about authentication (the token parameter), rate limits, error behavior, or what the returned coordinates look like. It is a bare one-line summary.

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?

It is a single short phrase with no waste, but this brevity stems from under-specification rather than disciplined conciseness. There is nothing to front-load beyond the core idea.

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 zero annotations, no output schema, and 0% parameter coverage, the description is far too thin to let an agent invoke the tool correctly. Authentication, input format, and return shape are all unaddressed.

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 coverage is 0%, so both the 'query' and 'token' parameters are undocumented anywhere. The phrase 'place text' loosely hints that query is free-form text, but the token's purpose and the expected input format are never explained, leaving the description well short of compensating for the 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 recognizable transformation (place text -> coordinates), which is more than a tautology of the name 'geo'. However, with many geocoding-adjacent siblings (food_place, ride_place, food_reverse) it never clarifies scope, provider, or what distinguishes it from those. Purpose is implied rather than stated with a specific verb+resource pairing.

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, nor any mention of prerequisites or the required token. An agent has no basis for choosing it over other place-related siblings.

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