APIbase

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

No annotations provided, so description carries full burden. It successfully discloses the data provider (Geoapify/OSM) and return format hint ('structured address data'), but omits rate limits, caching behavior, error handling for ambiguous addresses, and authentication requirements.

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?

Single, dense sentence front-loaded with action and scope. Every clause earns its place: input types, output coordinates, structured data component, and provider attribution. No redundant or filler text.

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 5 simple parameters with full schema coverage and no output schema, the description reasonably covers the tool's purpose and return value characteristics (lat/lon + structured data). Could be improved by noting that multiple ranked results may be returned (per the limit parameter), but adequate for the complexity level.

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 100%, establishing a baseline of 3. The description does not enumerate or elaborate on specific parameters (like explaining that 'type' filters result categories or that 'limit' controls pagination), but the schema handles this adequately without requiring description reinforcement.

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?

Description uses specific verb 'Convert' with clear input types (address, place name, landmark) and output (lat/lon coordinates + structured data). Implicitly distinguishes from sibling geo.address.reverse by specifying the forward direction (text-to-coordinates) and from other geocoding providers by naming Geoapify/OSM.

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?

Provides implicit usage context through input/output specification (forward geocoding), but lacks explicit guidance on when to choose this over sibling address.geocodio.geocode or when to use geo.address.autocomplete instead. No mention of prerequisites or filtering strategies.

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