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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the tool returns three duration types plus distance, but since an output schema exists that is largely redundant and it discloses nothing about rate limits, latency, or error behavior for a live external service.

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?

A single front-loaded sentence that leads with the resource and scope, then the return payload. No filler or repetition.

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?

With annotations covering the safety profile, a fully-described schema, and an output schema carrying return values, the description only needs to convey purpose and mode scope, which it does. It is essentially complete, though it could note the live external nature of the estimate.

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 baseline is 3. The description only echoes the mode dimension ('driving, and walking on request') and adds no syntax or default detail beyond what the mode and country parameters already document.

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+resource ('Apple Maps travel-time estimate between two points') and enumerates what it returns (live, historic, free-flow durations plus route distance). This clearly separates it from route/directions-oriented siblings, though the description itself never names an alternative sibling.

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?

Usage context is only implied: 'driving, and walking on request' hints at mode selection, and the routing advice ('use the directions endpoint for cycling') lives in the schema, not the description. There is no explicit when-to-use vs when-not statement in the description text.

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