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 only lists operation types and warns against inventing names; it does not state that add/set mutate the material library, what permissions are required, whether operations are idempotent, or what happens to existing materials.

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 two short sentences, front-loaded with the tool purpose and followed by a direct caution. It contains no filler, though it is quite terse for a seven-action multiplexed tool.

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?

An output schema exists and schema coverage is full, so return values and parameter details are covered elsewhere. However, for a multiplexed seven-action material tool with no annotations, the description omits action-dispatch semantics and mutation behavior, leaving the agent to rely heavily on enum names.

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 100%, so all parameters are already documented in the schema. The description adds no parameter-level detail beyond operation nouns such as list, add, and set, making the baseline 3 appropriate.

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 the resource (materials) and primary operations (list, add, set, query), so an agent can identify the domain. It does not name the specific action enum values or distinguish this tool from generic siblings like add or set_property, but the material scope provides useful differentiation.

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?

It gives one concrete workflow rule: 'list first if unsure', which helps avoid inventing material names. However, it does not explain when to use material_action versus sibling tools such as set_property or object_action, nor how to choose among the action variants, so usage guidance remains implied.

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