navigation_set_navmesh

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

No annotations are provided, so the description alone must convey behavioral traits. It mentions 'Set or bake' but does not disclose side effects (e.g., whether baking modifies the scene file, requires saving, or is destructive). The return value is noted, but deeper behavioral context is missing.

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 concise: a one-line purpose, a category, a clear argument list, and a return note. Every sentence contributes value, with no redundancy. The structure is front-loaded and easy to parse.

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 the tool has five parameters (three required) and an output schema, the description covers the basics but lacks completeness. It does not mention prerequisites like the existence of a navigation region node, nor does it clarify behavior when both navmesh_path and bake are provided. The return description is adequate but the behavioral gaps reduce completeness.

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?

Although the input schema has 0% description coverage, the description text provides one-line explanations for each parameter (e.g., 'navmesh_path: Path to a saved NavigationMesh resource (optional)'). This adds sufficient meaning beyond the bare schema titles, though some details (e.g., interaction between bake and navmesh_path) are omitted.

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 action: 'Set or bake a navigation mesh for a navigation region.' This verb+resource formulation is specific and distinguishes it from sibling tools like navigation_add_region, which adds a region rather than setting its navmesh.

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 explicit guidance on when to use this tool versus alternatives (e.g., navigation_add_region or navigation_add_agent). The description is straightforward but lacks context about prerequisites or conditions, leaving the agent to infer usage from the tool name alone.

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