create_material

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the operation ('Create') but doesn't disclose side effects, whether the material is added to the current scene, whether it becomes active/selected, or any error conditions. For a mutation tool with zero annotation coverage, this is a significant 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 compact and front-loaded with the core purpose. The Args list is efficient, though the 'properties' line is vague. No wasted words, but the lack of detail on 'properties' slightly reduces the value of the structure.

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 an output schema, return values are covered. However, the description lacks guidance on how 'properties' should be structured, what happens after creation, and how this tool relates to material application or inspection. For a creation tool with no annotations, this is incomplete.

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 does add brief meaning for 'name' and 'color' (noting color is optional and values are 0-1), but 'properties' is left as 'Optional additional material properties' with no detail on what keys or formats are expected. The description partially compensates but leaves a key parameter underspecified.

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 states a specific verb and resource: 'Create a new material in Cinema 4D.' This clearly distinguishes it from siblings like apply_material or inspect_redshift_materials, though it doesn't explicitly name those alternatives. The purpose is clear and actionable.

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 implies usage context (creating a material in Cinema 4D) but provides no explicit guidance on when to use this tool versus alternatives like apply_material or inspect_redshift_materials. It doesn't state exclusions or prerequisites, so an agent must infer the appropriate context from the tool name and sibling list.

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