rhino_layer_set_material

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

The description discloses the bridge-only nature and the read-only material table, adding context beyond the readOnlyHint=false annotation. It explains the effect (layer-source objects inherit the material) but does not mention destructive behaviors or auth needs, which are not critical here.

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: two sentences with no unnecessary words. The main action is front-loaded, and every sentence provides essential context (bridge-only limitation, prerequisite).

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?

Provides sufficient context for a simple binding tool: explains the bridge limitation, prerequisite, and effect. No output schema is visible but inferred. Could mention return value or error cases, but adequate given simplicity.

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 description adds no information about the parameters. While the schema itself has descriptions for doc_id, material_name, and material_index (including mutual exclusivity), the context indicates 0% schema coverage, so the description should compensate but fails to do so.

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 'bind' and the resource 'render material to a layer', and the phrase 'so layer-source objects inherit it' specifies the outcome. The distinct purpose is set apart from sibling layer tools (e.g., create, delete, set color).

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?

Explicitly mentions the bridge-only context, the prerequisite to use rhino_material_create first, and the limitation of the in-document material table being read-only. Provides clear when-to-use guidance, though no explicit when-not-to-use or alternative tools are mentioned.

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