Search delivery addresses

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds meaningful behavioral context: the action must be taken verbatim from `profile`, hand-crafting is forbidden, no confirmation token is required, and a loaded access token is needed. This goes well beyond annotation defaults.

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?

Three tight sentences: definition, use cases, and critical action/auth guidance. No fluff; all information is relevant and presented in logical order with the most important constraint (never hand-craft the action) front-loaded.

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 the rich output schema, comprehensive annotations, and clear 2-parameter schema, the description covers the essential operational details: purpose, workflow context, action provenance, read-only nature, and token requirement. Nothing critical is missing for an agent to select and invoke this tool correctly.

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%, with both `query` and `action` already well documented. The description mostly reinforces the schema's guidance about passing the action verbatim, so it adds little new parameter-level meaning beyond the structured 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?

States a specific verb ('Search'), a specific resource ('address database (zip/city)'), and the mechanism (server-provided addressSearchAction from `profile`). Clearly distinguishes its role from siblings like address_upsert and find_pickup_points by framing it as address suggestion/verification.

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 says when to use it: 'before address_upsert' or to 'verify a zip/city combination'. This gives clear context and points at the related sibling tool, though it does not state when not to use it or name an alternative tool for the same task.

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