find_navigation_path

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

No annotations exist, but the description fails to disclose any behavioral traits beyond the basic purpose. It does not mention whether the operation is read-only, what input validation occurs, or what happens with obstacles, leaving the agent with no useful behavioral cues.

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 extremely short (one sentence). While it avoids verbosity, it may be under-specified for the task. It is concise but not optimally informative.

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 that there is no output schema, the description should explain what is returned (e.g., a list of waypoints, a path). It does not. The description is incomplete for an agent to understand the tool's output and behavior fully.

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% and parameter descriptions in the schema are clear (start/end coordinates, auto-detected dimension). The tool description adds no additional meaning beyond what the schema already provides, so baseline score applies.

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 uses a specific verb ('Find') and resource ('navigation path'), clearly stating what the tool does. However, it does not differentiate from sibling tools like navigate_to or find_nearby_nodes, which may have overlapping functionality.

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?

No guidance on when to use this tool versus alternatives, nor any prerequisites or context provided. The agent receives no help in deciding between this and similar pathfinding tools.

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