autocomplete

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

Discloses that the tool returns partial matches not reliable coordinates, specifies the return format, and emphasizes it is a UI tool—all beyond the schema.

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?

Well-structured with clear sections (WHEN TO USE, DO NOT USE, FOCUS), front-loaded purpose, and no unnecessary sentences.

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?

Covers usage, return structure, and exclusions comprehensively, despite no output schema. Agent can confidently decide when to invoke.

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 100%, so baseline is 3. Description adds value by emphasizing focus parameters and distinguishing from geocode, but doesn't significantly augment parameter details beyond schema.

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 'Get real-time address suggestions as a user types in an input field' and distinguishes from siblings like 'geocode' by specifying it is a UI tool for live input.

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?

Explicitly states when to use ('ONLY for powering a live address input field') and when not to use ('DO NOT USE IN AGENTS'), and advises to pass focus.lat/focus.lon when location is available.

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