material_manage

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

No annotations are provided, so the description carries full burden. It discloses side effects (saving .tres, assigning materials, undo for apply_to_node), error conditions (overwrite=False errors if file exists), and parameter coercion (enum names to values, texture paths). It also explains the canonical call shape and compatibility alias, giving a complete behavioral model.

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?

While the description is long, it is meticulously structured with a summary followed by a bullet list of ops, each concisely specifying signature and semantics. Every sentence adds value—no fluff. The canonical call shape at the end is a useful structural aid. Front-loaded with a clear definition.

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's complexity (8 ops) and the sparse schema, the description is exceptionally complete. It covers all ops, their parameters, side effects, resource-form usage, and error handling. Since an output schema exists, return values need not be explained, and the description focuses on what the agent needs to select and invoke correctly.

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 input schema is degenerate (only op, params, session_id) with 0% coverage of actual parameters. The description fully compensates by listing each op's parameters with types, defaults, and allowed values (e.g., type: 'standard' | 'orm' | 'canvas_item' | 'shader', slots: 'override' | 'surface_<N>' | 'canvas' | 'process'). It even clarifies how values like colors/vectors are passed and that texture properties accept res:// paths.

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 tool's purpose: 'Material authoring (StandardMaterial3D, ORMMaterial3D, ShaderMaterial, CanvasItemMaterial)' and enumerates specific ops (create, set_param, assign, etc.). It distinguishes from siblings by focusing exclusively on materials and their properties, not general resources or scenes.

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?

The description gives explicit guidance on when to use the resource form ('godot://materials — prefer for active-session reads') and details each op's parameters and behavior. However, it doesn't explicitly state when NOT to use this tool in favor of a sibling (e.g., resource_manage), so the alternatives are implied rather than directly contrasted.

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