bake_navigation_mesh

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

Without annotations, the description carries full burden. 'Bake' implies a potentially expensive or irreversible operation, but no side effects, performance impact, or success/failure conditions are disclosed. The agent cannot anticipate the tool's behavior fully.

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?

Single sentence, no wasted words. However, it is too brief to convey important context, trading conciseness for completeness. Still efficient given the tool's specificity.

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?

No output schema, so description should explain return values or process. Baking a navigation mesh may have status or errors, but none mentioned. The tool is one of many navigation siblings, requiring more context for correct invocation, but description is minimal.

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%, so the schema already documents both parameters. The description adds no extra meaning beyond the schema's field descriptions. For the 'properties' object, 'etc.' hints at common keys but is vague. Baseline 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 states a specific action ('bake') and resource ('navigation mesh for a NavigationRegion'), making the purpose clear. However, it does not distinguish from sibling tools like 'setup_navigation_region' or 'find_navigation_path', missing explicit differentiation.

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. It does not mention prerequisites (e.g., region must exist) or exclusions. The agent has no context to decide between this and other navigation-related tools.

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