godot_draw_debug_shapes

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

The description adds meaningful behavioral context beyond the annotations by explicitly stating shapes are temporary and have durations. It does not discuss whether previous shapes are cleared or whether rendering requires a running game, but it meaningfully discloses lifetime behavior that the sparse annotation flags do not convey.

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?

A single sentence that front-loads the action and resource with no filler. It is appropriately concise for an overview, even though the underlying schema is complex.

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 complex input—an array of shape specs with multiple 2D/3D coordinate variants and nine properties—the description is too terse. It omits any high-level guidance on shape selection, coordinate conventions, when to use 2D vs 3D shapes, or the relationship to godot_clear_debug_shapes. The schema helps, but the description does not provide the contextual framing an agent needs.

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?

The description adds only high-level hints about 'colors' and 'durations', while the input schema provides detailed per-field descriptions for shape_type, position, size, radius, start/end, text, and other properties. The schema carries most of the parameter meaning, and the description does not mislead, so this is acceptable but not compensatory.

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?

States a specific action ('Render') and resource ('2D/3D debug shapes') with key attributes ('temporary', 'colors', 'durations'). It is clear what the tool does, though it does not explicitly contrast itself with sibling godot_clear_debug_shapes or other debug-rendering 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?

No guidance on when to use this tool versus alternatives like godot_clear_debug_shapes, godot_set_physics_debug_mode, or godot_cast_ray_3d. The description states only the action, leaving the agent to infer appropriate usage contexts such as visualizing debug geometry during development or testing.

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