Maps Open Directions In Maps

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

The description adds no behavioral insight beyond what the annotations already provide. It says nothing about side effects, such as opening the Maps app or launching navigation, and the annotations (openWorldHint, idempotentHint, destructiveHint) are minimal. There is no contradiction, but there is also no meaningful behavioral disclosure.

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?

The description is short, but this is under-specification rather than effective conciseness. Every word spent on 'Delegated Apple domain tool' and 'exposed through Apple-Tools-MCP' could have been replaced with actual functional information.

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 sibling context with multiple maps tools and a 3-parameter schema, the description is completely inadequate. It fails to explain the behavior, the required input semantics, or how this tool differs from closely related direction tools.

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%, so the description needed to explain the parameters but does not. It offers no guidance on what 'destination' or 'origin' should look like, nor what values 'transport' accepts beyond the default 'driving'.

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 merely restates the tool name in quotes ('Delegated Apple domain tool 'maps_open_directions_in_maps' exposed through Apple-Tools-MCP') and gives no indication of what the tool actually does. It lacks a specific verb and resource, and does not distinguish this from sibling direction-related tools like maps_get_directions or apple_maps_get_directions_strict.

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?

There is no guidance on when to use this tool versus alternatives. No conditions, exclusions, or mention of sibling tools are provided, so an agent cannot determine whether to choose this over maps_get_directions or maps_build_maps_link.

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