Render Google Maps directions

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds meaningful behavior: it returns directions data, conditionally renders in MCP Apps view, and explicitly clarifies it does not navigate or mutate the browser session—valuable context beyond the annotations.

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 sentences, front-loaded with the core purpose, and no wasteful words. Every clause contributes either to purpose, rendering behavior, or display-only guarantee.

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?

No output schema exists, so the description should explain return values. It says 'directions data' but does not detail the data structure. It also leaves the 'when Google Maps Embed is configured' condition somewhat ambiguous. Given the tool's moderate complexity, it is acceptable but has clear gaps.

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 0% and the description only mentions 'origin/destination' generically, without naming the exact parameters or explaining the 'mode' enum. It adds minimal meaning beyond the schema, leaving the agent to infer parameter semantics from parameter names alone.

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 opens with 'Return explicit origin/destination directions data', a specific verb-resource pair. It distinguishes itself by noting 'Display-only: this does not navigate or mutate the dedicated browser session', which contrasts with sibling tools like maps_directions that likely perform navigation.

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 clearly states this is for returning directions data and rendering in an inline MCP Apps view when configured, and explicitly says it does not navigate or mutate the browser session. This gives clear context for when to choose this read-only variant, though it does not explicitly name alternative tools or exclusion criteria.

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