setup_navigation_agent

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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: only the provided pathfinding and avoidance properties are applied, implying no changes to other agent properties. However, it omits important details such as what happens if the node already exists, default naming, whether it overwrites, and any failure modes. Some transparency is provided, but significant gaps remain.

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, well-structured sentence with no redundant words. It front-loads the action and resource, then qualifies the behavior. Every word earns its place, making it highly concise and readable.

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 11 parameters, no annotations, and no output schema, the description is far from complete. It does not explain parameter defaults, the meaning of 'mode' auto, interaction with parent nodes, or result feedback. The description suffices only for a high-level understanding and would leave an agent guessing on details critical for correct invocation.

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%, leaving the description to compensate. It categorizes properties as 'pathfinding and avoidance' but does not explain any of the 11 parameters (e.g., mode, radius, max_speed) or how they map to the agent. This provides minimal semantic value beyond the schema's bare parameter names.

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 action ('Add') and the resource ('NavigationAgent2D or NavigationAgent3D'), along with the placement ('under a parent node') and scope ('applying only the pathfinding and avoidance properties given'). This distinguishes it from sibling tools like setup_navigation_region or bake_navigation_mesh, making the purpose unmistakable.

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 guidance on when to use this tool versus alternatives. It does not mention any preconditions, such as the parent node existing, or contrast with generic add_node or navigation-specific tools. The description only states what it does, not when to choose it over siblings.

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