load_sprite

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

Discloses side effects ('Saves automatically') and validation behavior (node type and file existence checks). The annotations provide idempotentHint: true, which aligns. Minor omission: does not specify if previous saves are overwritten or if return values indicate success.

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?

Four concise sentences, each serving a purpose: purpose, usage guidance, save behavior, error conditions. No fluff, front-loaded with the core action.

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?

No output schema, but the description covers usage context, side effects, and error conditions. It lacks explicit return value information, but for a setter-like tool, this is acceptable. Overall complete for the tool's 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 coverage is 100%, so baseline is 3. The description adds useful context for texturePath ('must be a real file under projectPath'), enhancing understanding beyond the schema descriptions.

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: 'Set the texture on an existing Sprite2D, Sprite3D, or TextureRect node.' It distinguishes this tool from siblings by explicitly contrasting with add_node for new nodes.

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?

Provides explicit guidance: 'Use this when the node already exists; for new nodes, pass texture via add_node properties.' Also mentions automatic saving and error conditions, helping the agent decide appropriately.

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