write_material

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose that work_dir honors client roots, which is a useful behavioral trait. However, it does not mention whether files are overwritten, permissions required, or what happens on error. For a write operation, this is a moderate gap.

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 short and front-loaded with the main purpose. However, it is under-specified; while it has no wasted words, it omits critical details. It is not verbose but also not appropriately concise for a tool with seven parameters and zero schema descriptions.

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?

Given the tool has 7 parameters, no schema descriptions, no annotations, and only a brief description, it is far from complete. The agent would need to infer the meaning of 'channels' and 'channel_type' and the expected file format, which are not explained. This is a significant gap for a write operation.

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 0%, so the description must compensate. It only explains material_type (0=glass,1=plastic). The other six parameters (channels, channel_type, roughness, specularity, name, work_dir) are not explained at all, leaving the agent to guess their meaning from names alone. This is minimal added value beyond the schema.

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 (write) and resource (Radiance material .rad file(s)), and gives a specific mapping for material_type (0=glass, 1=plastic). It is specific enough to distinguish from many siblings, though it does not explicitly name alternatives. It is clear but not maximally differentiated.

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?

No guidance is provided on when to use this tool versus alternatives. The description simply states what it does, leaving the agent to infer context from the name and sibling list. There is no mention of prerequisites, typical use cases, or exclusions.

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