Geocode a US address

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

With no annotations available, the description carries the burden of behavioral disclosure. It usefully mentions the free nature, lack of API key, and data source (Census Bureau), but does not disclose rate limits, error behavior, or output format details beyond the listed geographies.

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 concise, using two short sentences and a source attribution. It front-loads the core action and adds only necessary context about cost and source, with no waste.

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?

For a single-parameter tool with no output schema, the description adequately outlines the input and expected outputs (lat/long, geographies). It could be more complete by explaining potential failure modes or usage limits, but overall it is sufficient for basic invocation.

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 already fully describes the 'address' parameter with an example, so the description adds little parameter-specific meaning. The mention of 'US street address' reinforces the schema but does not go beyond it.

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 clearly states the tool's function: converting a US street address into latitude/longitude and Census geographies. This specific verb+resource distinguishes it from sibling tools that operate on census tracts or zones rather than addresses.

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 implicitly indicates this is for address-to-geography conversion, which contrasts with siblings like lookup_census_tract or check_flood_zone. It does not explicitly exclude other use cases or name alternatives, but the context is clear.

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