blend-ai

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. While it states this is a creation operation (implying mutation), it doesn't mention permissions needed, whether the material becomes active/assigned, what happens if a material with the same name exists, or any side effects. The return format is mentioned but without details about error conditions or confirmation structure.

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 efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence serves a purpose with minimal waste. The only minor improvement would be integrating the purpose more seamlessly rather than separating it into distinct sections.

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?

For a single-parameter creation tool with an output schema, the description covers the basics: what it creates and what parameter it needs. However, with no annotations and sibling tools like 'create_principled_material' that appear similar, more context about differentiation and behavioral details would be helpful. The output schema reduces the need to describe return values, but mutation tools typically need more behavioral transparency.

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?

With 0% schema description coverage and only one parameter, the description provides essential semantic context: 'name' is for 'Name for the new material.' This clarifies the parameter's purpose beyond the schema's bare type information. However, it doesn't mention constraints like length, allowed characters, or uniqueness requirements that might be relevant.

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 specific action ('Create a new material') and specifies the resource type ('with a Principled BSDF shader node'), distinguishing it from sibling tools like 'create_principled_material' (which appears to be a similar but distinct tool) and 'assign_material' (which applies existing materials). The verb+resource combination is precise and unambiguous.

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 like 'create_principled_material' (which appears functionally similar) or 'duplicate_material'. There are no prerequisites mentioned, no context about when this tool is appropriate, and no exclusions or warnings about when not to use it.

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