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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds the constraint that all three location parameters (lat, lon, address) are required, which is useful but not beyond what annotations already convey about safety. No additional behavioral traits are disclosed.

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 concise sentences plus an illustrative example. The key purpose is front-loaded, and every sentence adds value. No unnecessary words.

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 tool's simplicity, with 6 parameters fully described in schema and annotations covering safety, the description is mostly complete. It explains the core functionality and the critical requirement for all three location fields. However, it does not describe the structure of the response (e.g., format of scores and description), which would be helpful since no output schema exists.

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% with detailed descriptions for each parameter. The description goes further by explaining the relationship between coordinates and address: 'the coordinates locate the point and the address disambiguates it.' This adds semantic value that helps the agent understand why all three are needed.

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 returns Walk/Transit/Bike scores (0-100) plus a human-readable description. It uses specific verbs and resources, and the purpose is distinct from all sibling tools, which focus on other domains like research or entity profiles.

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 includes a NOTE that lat, lon, and address must all be provided, and gives an example. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it. Since no sibling tools offer similar functionality, this is a minor gap.

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