textures-load

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

No annotations are provided, so the description carries the full burden. It states the action but doesn't disclose side effects (e.g., whether it replaces an existing datablock with the same name, whether it loads into the current blend file, or if it requires specific permissions). The term 'load' implies a read operation, but the tool likely creates a new datablock, which is a mutation. This ambiguity is a gap.

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, concise sentence that is front-loaded with the action. It avoids fluff and is easy to parse. However, it could be slightly more informative without becoming verbose, so it doesn't earn a 5.

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 2 parameters, no output schema, and no annotations, the description is too sparse. It doesn't explain the return value (e.g., the created datablock name), error conditions (e.g., file not found), or how it integrates with the texture pipeline. Sibling tools like textures-list and textures-report exist, so the description should clarify how loading fits in. The description is minimally viable but leaves significant gaps.

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 0%, so the description must compensate. It mentions 'image datablock' and 'disk' but doesn't explain the 'name' parameter's role (optional name for the datablock) or the 'path' format. The schema provides titles but no descriptions, so the tool description adds minimal value beyond the parameter names. Baseline 3 is appropriate because the description at least clarifies the purpose of the tool, but it doesn't detail parameter semantics.

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 'Load an image datablock from disk' clearly states the action (load) and resource (image datablock) with a source (disk). It distinguishes from sibling tools like textures-list and textures-report, which are for listing/reporting, not loading. However, it doesn't explicitly mention that it creates a new datablock or how it relates to existing textures.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., file format support, whether the path must be absolute), nor does it contrast with textures-list or textures-report. The agent must infer usage from the name and schema.

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