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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the use of OSM Nominatim as the source, but does not disclose potential rate limits, usage terms, or whether an API key is required. For a geocoding service, such details are important, and the description is silent on them.

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 a single, front-loaded sentence that conveys the purpose without any filler. Every word earns its place, and the core functionality is immediately clear.

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?

The tool is simple (one parameter) and has an output schema, so return structure is covered. However, the description lacks details about edge cases (e.g., ambiguous or unmatched place names) and any usage limitations. Given the absence of annotations, more context could be provided to ensure correct invocation, but the basic purpose is adequately conveyed.

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 schema has one parameter 'q' with no description and 0% coverage. The description implies 'q' is the place name ('Place name → coordinates'), adding some meaning beyond the bare schema. However, it does not specify the expected format (e.g., full address, city name) or clarify the default empty string. It partially compensates for the missing schema documentation.

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 verb ('Geocode') and resource ('Place name → coordinates') and specifies the data source (OSM Nominatim). This makes the tool's purpose unambiguous and distinguishes it from reverse geocoding (revgeocode) and other coordinate-related tools.

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 description implies the tool is for forward geocoding (place name to coordinates) but does not explicitly mention when to use it over alternatives like revgeocode or geodist. No exclusions or alternative conditions are provided, so the guidance is only implied.

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