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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral context by stating that output includes an accuracy score and type and that optional data fields can be appended.

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?

Two focused sentences plus a concrete example, with the main action and output front-loaded. Every sentence earns its place, and the example demonstrates required parameters and optional fields compactly.

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?

Together with the schema, the description provides enough to invoke the tool correctly: required q and _apiKey, optional fields, limit and country, and the output type. A small gap is that it doesn't describe the response structure beyond accuracy/type, but that is minor for a simple geocoding call.

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%, so the schema already documents all five parameters. The description adds only mild benefit by showing a concrete example and mentioning fields like census/FIPS, but it doesn't need to compensate for any schema gaps.

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 states a specific verb (forward geocode), a specific resource (a single address), and the output (latitude/longitude with accuracy score and type). It also distinguishes from reverse geocoding and batch variants by explicitly saying 'single address', so an agent can tell it apart without opening the schema.

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 phrase 'forward geocode a single address' gives clear context that this tool is for one-address lookups, implying batch or reverse alternatives are handled elsewhere. It doesn't explicitly name alternatives or exclusions, but the context is clear enough to route correctly.

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