manage_navigation

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

Annotations indicate readOnly=false, destructive=false, and idempotent=false, but the description adds no additional behavioral context such as side effects of rebuild_navigation, the save option, or operation-specific impacts. For a tool with multiple distinct actions, this is a transparency gap.

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 a single concise sentence that avoids unnecessary verbosity. However, it's a high-level summary rather than a structured overview, and could be improved by referencing the required 'action' parameter to help the agent navigate the tool's complexity.

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 high complexity (42 parameters, 12 actions, no output schema), the description is far too sparse. It doesn't map parameters to actions, mention the required action parameter, or explain the differences between link types. A more comprehensive description is needed to fully guide the agent.

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?

The schema includes all 42 parameters with individual descriptions (100% coverage), so the schema already provides thorough parameter semantics. The tool description adds no extra meaning beyond what the schema offers, so the baseline score of 3 is appropriate.

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 it configures NavMesh settings, adds nav modifiers, and creates nav links/smart links for pathfinding, making the tool's purpose evident. However, it doesn't differentiate this from sibling tools like manage_ai or control_actor, so it's clear but lacks sibling distinction.

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, nor are there any exclusions or prerequisites. The description only lists capabilities without contextual use cases, leaving the agent to infer appropriate usage.

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