game_canvas

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it only offers mutating verbs ('Create/configure'). It does not disclose that configure likely requires an existing node, what happens on repeated calls, how layer ordering behaves, or any side effects on the scene tree. The schema's action list is not expanded with behavioral context.

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 five words with zero waste and front-loads the two target node types. However, it is lean to the point of under-specification for a tool with six parameters and three action modes; it is terse rather than efficiently informative.

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?

This tool combines six parameters, three action modes, two node types, no annotations, and no output schema, which demands a substantive description. The current text doesn't explain what each action does, prerequisites for configure, how name/parentPath resolve, or the result of each call. An agent must guess behavior from parameter names alone, which is inadequate for this complexity.

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 100%, so the baseline is 3 since the schema documents all six parameters. The description adds marginal value by implicitly linking the node types to action values (CanvasLayer→create_layer, CanvasModulate→create_modulate), which aids enum disambiguation, but it adds no detail on parameter relationships, defaults, or format expectations.

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 verb ('Create/configure') and concrete resources ('CanvasLayer and CanvasModulate'), two distinct Godot node types. This makes the tool's domain immediately clear and separates it from most siblings like game_light_2d or game_tilemap. However, it doesn't explicitly differentiate from the similarly-named game_canvas_draw sibling, and the action parameter's role is implied rather than stated.

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 usage context is provided. The description doesn't say when to use CanvasLayer vs CanvasModulate, doesn't reference alternatives such as game_canvas_draw or manage_layers, and lists no prerequisites or conditions. An agent must infer when this tool applies purely from the action enum values in the schema.

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