Assign Material (Texture Tag)

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

With no annotations, the description must carry the behavioral burden, and it does: it states that a Texture tag is created, that an existing tag can be updated when update_if_exists is true, and that projection aliases avoid raw TEXTURETAG_* ids. It does not detail failure modes or duplicate-tag behavior when update_if_exists is false, but the core mutation and side effects are disclosed.

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: the first identifies the primary action and update behavior, and the second adds value by summarizing projection aliases. No filler or redundant restatement of the tool name.

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 mutating tool with no annotations and no output schema, the description covers the essential behavior, the update path, and the projection vocabulary. It does not mention failure behavior or what the response contains, but these are secondary for such a straightforward assignment action.

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 coverage is 100%, so a score of 3 is the baseline, but the description adds meaningful context beyond the schema: the projection alias list clarifies that the enum values are aliases, and the update_if_exists behavior is linked to the tag-creation workflow. This helps the agent understand parameter intent without opening the full 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 states a specific verb and resource: 'Link a material to an object by creating a Texture tag.' This clearly distinguishes it from material-creation and layer-assignment siblings such as rs_create_material and assign_to_layer.

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?

The core use case is clear: assigning a material to an object via a Texture tag. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough that an agent can infer when to invoke it.

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