Set Redshift PBR Material

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

With no annotations, the description carries the behavioral disclosure burden. It usefully discloses that texture paths are prevalidated and that replace_graph requires an explicit document and reliable rollback support. However, it does not explain what replace_graph actually does, what failure modes exist, or whether the operation is undoable, leaving significant behavioral gaps.

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 sentences with little wasted text, and the most important constraint (replace_graph needs document and rollback support) gets its own sentence. Some phrasing such as 'reliable rollback support' is vague, but overall the size is appropriate.

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 mutation tool with 8 parameters, deeply nested channel objects, no annotations, and no output schema, this description is not complete enough. An agent would need external knowledge or schema inference to understand what each PBR channel accepts and what actually happens when replace_graph is true or false.

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 only 25%, so the description needed to compensate for the many undocumented parameters. It does not define base_color, roughness, metalness, normal, or displacement beyond the generic 'PBR channels' phrase. It adds a small amount of meaning around replace_graph and the document requirement, but not enough to make 8 nested parameters understandable.

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 a specific action ('Patch') and resource ('supplied Redshift Standard Material PBR channels'), making it clear this edits an existing material rather than creating or assigning one. It does not explicitly name a sibling alternative, but the wording itself delineates the purpose from rs_create_material and assign_material.

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?

There is no explicit when-to-use or when-not-to-use guidance. 'Supplied' implies the tool targets an existing material, but it does not tell the agent when to choose this over set_params, rs_create_material, or assign_material. The replace_graph requirement is a constraint, not a routing guideline.

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