resource_create_material

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

The description explains parameter behaviors (e.g., roughness range, transparency modes) but does not disclose potential side effects such as whether an existing file at save_path is overwritten, or what happens if assignment fails. No annotations are present, so the description bears full responsibility.

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 concise: a one-line purpose, a category tag, and a clear list of parameters with explanations. No unnecessary words; front-loaded with the key action.

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?

The description covers all parameters and the optional assignment feature. It is complete for a 12-parameter tool with an output schema, though it lacks details on error handling or prerequisites (e.g., project must exist).

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, the description provides thorough meaning for all 12 parameters, including types, defaults, allowed values (e.g., transparency modes), and ranges (e.g., roughness 0.0-1.0). This adds significant value beyond the schema's type-only definitions.

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 creates a StandardMaterial3D resource and optionally assigns it to a node. This specific verb+resource combination distinguishes it from sibling tools like resource_list (list) or resource_get_material_properties (get).

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?

Usage is implied by the name and description, but there is no explicit guidance on when to use this tool versus alternatives like resource_list or other creation tools. No alternatives or exclusions are mentioned.

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