octane_create_material

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

No annotations are provided, so the description must carry the behavioral burden. It discloses key traits: queuing (asynchronous), forwarding of non-default PBR fields, and graceful handling of unavailable pins with warnings instead of crashes. This adds valuable context beyond a simple 'create' statement.

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 very concise: two sentences in the first paragraph and two in the second. Every sentence provides distinct value (purpose, forwarding, error handling). No extraneous content.

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?

Despite having 13 parameters and 0% schema coverage, the description is only a few lines. It lacks explanations of material kinds, color format, texture paths, or return values (output schema exists but is not referenced). The description is insufficient for an agent to correctly use all parameters.

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 only mentions 'optional PBR fields' and the forwarding behavior of non-default values, but does not explain individual parameters (e.g., ior, kind, color) or their expected formats. The agent must rely entirely on parameter names and types, leading to a weak semantic contribution.

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 it queues a material creation/update command with optional PBR fields. The verb 'queue' and resource 'material' are specific, and it distinguishes from sibling tools like octane_assign_material by focusing on material definition rather than assignment. However, the dual 'creation/update' may cause slight ambiguity since the tool name only mentions creation.

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 explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions for update vs creation, or differentiation from siblings like octane_assign_material. Usage is only implied through the purpose statement.

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