set_material_property

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

The only annotation is idempotentHint: true, which already covers idempotency. The description adds no behavioral details beyond listing property names; it doesn't mention validation, error handling, or effects on other properties (e.g., emission_color interacting with emission_strength). Since the annotation is present, a score of 3 is reasonable, but the description contributes little extra transparency.

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 that front-loads the purpose and enumerates valid property names. It wastes no words, though it could be structured with bullet points or value-type hints. Still, it is efficient and direct.

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 tool is a straightforward setter with an output schema (though not provided here). The main missing context is the value format per property, which is critical for correct invocation. Since it's a simple setter, the description is mostly complete but lacks essential parameter semantics, so it falls short of full completeness.

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 schema has 0% description coverage, so the description carries the full burden for parameter semantics. It lists property names but does not specify expected value formats (e.g., base_color as an RGB array, metallic as a float, normal_strength as a float). The schema's 'value' is loosely typed (anyOf number/array), so an agent cannot know the correct shape for each property without external knowledge. This is a significant 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 verb 'Set' and the resource 'a Principled BSDF property', and enumerates all supported property names. This distinguishes it from sibling setters like set_modifier_property or set_light_property, so an agent can identify its scope without ambiguity.

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 provides no guidance on when to use this tool versus alternatives such as batch_set_property (which likely sets multiple properties at once) or set_material_info. There are no explicit conditions, exclusions, or references to siblings, leaving the agent to infer the appropriate context.

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