shading.assign_material

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

Discloses the side effect of creating the material if missing, which adds behavioral context beyond a simple assignment. However, does not specify what happens if the object doesn't exist, if it overwrites existing material, or error handling.

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?

Extremely concise single sentence with no fluff. Parenthetical clarification is efficient. All words are meaningful.

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 simple assignment tool with only two string parameters, the description covers the core functionality. However, it lacks information about return values, accepted naming conventions, scope (single vs multiple objects), and potential errors. Given absence of output schema, more detail would be beneficial.

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 has descriptive titles for both parameters ('Object to receive the material', 'Material name (created if it does not exist)'), but description adds no additional detail. With 0% schema description coverage, the description should compensate with parameter-level info, which it does not.

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?

Clearly states it assigns a material to an object and creates the material if missing. Distinguishes from sibling 'shading.create_material' by combining assignment with creation, but doesn't explicitly contrast with other tools.

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?

Implies usage for assigning materials, but no explicit guidance on when to use vs alternatives (e.g., 'shading.create_material' or 'shading.set_principled'). No prerequisites or context provided.

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