create_material

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. It mentions that nodes are enabled, which is a notable trait, but it does not describe side effects, prerequisites, whether the new material becomes active, or any other behavioral implications. The absence of annotations and the minimal description leave significant gaps for a creation operation.

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 with no extraneous words. It front-loads the core purpose ('Create a new material') before adding the qualifier about nodes. Every word earns its place, and the structure is efficient.

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 the simplicity of the tool (one parameter) and presence of an output schema, the description is insufficient. It lacks any parameter guidance, usage context, or elaboration on what 'nodes enabled' implies. The agent is left without enough context to confidently invoke it, especially given the many sibling material tools.

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?

The input schema contains one required property 'name' with no description, type, or default, and schema description coverage is 0%. The description does not mention the parameter at all, so it provides no meaning beyond the property key. An agent has no idea what format 'name' should take (string, identifier, etc.) or its significance, making this a critical gap.

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 ('Create'), the resource ('a new material'), and a specific feature ('with nodes enabled'). This distinguishes it from many sibling tools like create_camera or create_light, and from material-specific variants like create_emission_material or create_glass_material, though it doesn't explicitly compare to them. It is a specific, unambiguous statement of purpose.

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?

There is no mention of when to use this tool versus alternatives. It does not state exclusions or contexts where other material-related tools (e.g., assign_material, create_emission_material) should be used instead. The intended usage is only implied by the tool's name and description, with no guidance to help an agent choose correctly.

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