navigation

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

Annotations indicate mutation (readOnlyHint false), but description does not elaborate on side effects, permissions required, or whether actions are reversible. The description adds minimal behavioral context beyond the action list.

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 very short (two sentences) and includes the key actions. However, it relies on the help tool for completeness, which undermines self-contained clarity. Still, it is efficient.

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 8 parameters and no output schema, the description is insufficient. It does not explain how parameters apply to each action (e.g., radius for agents vs obstacles). The agent would need the help tool to fully understand usage.

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?

All 8 parameters are documented in the schema, so baseline is 3. The description does not add meaning beyond the schema (e.g., relationship between radius and action). Deferring to help tool reduces value.

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 clearly states the tool's purpose: creating navigation regions and adding agents/obstacles. It lists the specific actions, which differentiates it from sibling tools like 'nodes' or 'scenes'. However, it could be more precise about the context (e.g., Godot navigation system).

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 is provided on when to use this tool versus alternatives like 'nodes' or 'physics'. It defers to the help tool, leaving the agent to guess the appropriate usage context.

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