Create Redshift Material

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

The description does disclose one non-trivial behavior: it can reuse an exact-name match if requested, which goes beyond the bare create semantics in the title. However, with no annotations available, it leaves important behavior undisclosed, such as what happens when an exact-name match exists but reuse is not requested.

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?

A single sentence that front-loads the primary create action and then adds the conditional reuse behavior. There is no filler, repetition, or unnecessary detail.

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 description is adequate for a simple create tool, but because there are no annotations and no output schema, the agent is left uncertain about duplicate-name conflict behavior and return values. The schema covers parameters, but the operational contract is incomplete.

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 the schema already documents all parameters. The description lightly echoes the update_if_exists behavior with 'reuse one exact-name match when requested', but it does not add significant meaning beyond the schema's own parameter descriptions.

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?

States a specific action and resource: create a Redshift node material, with a conditional reuse behavior for exact-name matches. This distinguishes it from sibling tools like assign_material, which attaches materials, and rs_set_material_pbr, which sets PBR material properties.

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 explicit when-to-use or when-not-to-use guidance is provided, and no alternatives are named. The only usage hint is the conditional phrase 'when requested', which is vague and does not tell the agent how to decide between this tool and related material tools.

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