godot_configure_navigation_obstacle

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

Annotations already indicate this is a mutating, non-idempotent operation, so the description adds only the 'dynamic avoidance' context. It does not disclose whether the tool creates or modifies a node, how existing settings are affected, or any side effects beyond the annotation flags.

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, front-loaded sentence with no filler or repetition. It is appropriately concise for the small amount of information it conveys, though it sacrifices substance for brevity.

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 the tool has many nested parameters and no usage guidance, the description is incomplete. It does not explain when to configure an obstacle, how the parameters interact, or what the output schema represents. The rich schema descriptions compensate partially, but the tool-level context is missing.

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 reported as 0%, and the description provides no parameter-level meaning. It does not mention radius, velocity, vertices, node paths, or avoidance layers, leaving the agent to rely entirely on the schema's nested descriptions without any high-level guidance.

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 names a specific verb ('Configure') and resource ('NavigationObstacle2D or NavigationObstacle3D'), and adds the scope 'dynamic avoidance,' which distinguishes it from broader navigation tools like godot_create_navigation_region. It is clear and unambiguous, though it does not explicitly contrast with sibling tools.

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 such as godot_create_node, godot_modify_node, or godot_create_navigation_region. The description implies usage for configuring obstacles but provides no context, prerequisites, or exclusions.

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