maps_direction_walking_by_coordinates

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

Discloses distance constraint (100km) and return fields (distance, duration, details). No annotations, so description carries full burden. Lacks details on authentication, rate limits, or side effects.

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?

Efficiently structured with a brief overview and parameter descriptions. Could be slightly more concise, but no wasted sentences.

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?

Covers input format, distance limit, and return fields (distance, duration, navigation details). With no output schema, this is adequate. Could add more detail on return structure.

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 has 0% coverage, but description adds format ("经度,纬度") and example. This compensates well for the lack of schema descriptions.

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?

Clearly states it's for walking path planning using start/end coordinates, within 100km. Distinguishes from siblings by specifying coordinate-based and walking mode.

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?

Implied usage: for walking, by coordinates, up to 100km. No explicit when-not-to-use or alternatives, but sibling tools are present for other modes.

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