bake_navigation_mesh

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutating operation ('Bake') and mentions the side effect of optional 2D region rebuilding, but does not disclose details like whether existing meshes are overwritten, prerequisites, or potential performance implications.

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 sentence that immediately states the core action and resource. It is concise, with no redundant phrases or extraneous details, effectively front-loading the most important information.

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?

Despite the tool's moderate complexity, the description omits key context such as whether the node must already exist, what happens if baking fails, and expected return values. There is no output schema to clarify results, and no mention of related setup steps, making it incomplete for a navigation mesh baking operation.

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 description coverage is 0%, so the description must compensate. It adds meaning to the 'outline' parameter by explaining it triggers 2D region rebuilding, but it does not clarify the expected format of outline items or elaborate on 'node_path' beyond its obvious schema name.

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 'Bake' with a clear resource ('navigation mesh or polygon') and scoping ('of a NavigationRegion2D/3D'). It also distinguishes this from sibling tools like setup_navigation_region by indicating this performs the actual baking computation.

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?

The description provides context on the optional outline parameter ('optionally rebuilding the 2D region'), but does not explicitly state when to use this tool versus alternatives or any preconditions. It lacks explicit 'when not to use' guidance or mention of related tools like setup_navigation_region.

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