navigation_add_agent

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

No annotations provided. Description only says it adds an agent and returns success/error. No disclosure of side effects, idempotency, or required scene state. As a creation tool, more behavioral context is needed.

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?

Description is well structured with Args and Returns sections, and purpose is front-loaded. A bit verbose but no redundant 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?

For a tool with 7 parameters and no annotations, the description covers basics but lacks detail on constraints (e.g., name uniqueness), behavior on existing nodes, and precise return format. Output schema exists but is only vaguely described.

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 0%, but the description provides explanations for all 7 parameters including defaults and allowed values (e.g., agent_type). This adds significant meaning beyond the schema.

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 'Add a navigation agent to a scene' with specific verb and resource. The category 'Navigation' and context of sibling tools like navigation_add_obstacle and navigation_add_region confirm distinct purpose.

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 explicit guidance on when to use this tool versus alternatives. Does not mention when to choose agent over obstacle/region, nor prerequisites or conditions.

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