delete_material

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

With no annotations available, the description carries the full burden of behavioral disclosure. It only states the action itself and gives no information about side effects (e.g., whether the material is removed from all objects using it), error conditions, or behavior when the material does not exist. This is insufficient for a mutation tool.

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 a single, direct sentence with no wasted words. It is front-loaded with the action verb and target, making the core purpose immediately clear and easy to parse.

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?

While the tool is simple and has an output schema (so return values may be documented elsewhere), the description lacks contextual information such as the effect on object material slots, whether deletion is reversible, and any constraints on usage. It also does not differentiate itself from related material tools (e.g., set_material_slot, assign_material) in terms of when to delete versus reassign.

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 schema has zero documentation for the 'name' parameter, and the description provides no additional meaning. It does not clarify what type of name is expected (e.g., data-block name, display name), whether it is case-sensitive, or whether the material must be unique. The agent must infer everything from the tool name, which is risky.

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 clear, specific verb ('Remove') and resource ('material') with a precise location ('bpy.data.materials'). This unambiguously distinguishes it from sibling delete tools like delete_object or delete_collection, leaving no doubt about what is being operated on.

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 about when to use this tool versus alternatives. The description does not mention prerequisites, fallback options, or conditions that would select this tool over related tools like assign_material or set_material_slot. An agent has no context for choosing it appropriately.

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