armorpaint_import_material

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

All annotations are false, so they provide no safety or behavioral profile. The description only says 'import into the current project' and does not disclose whether the import overwrites existing materials, merges with them, requires an already-open project, or what side effects may occur. For a mutating operation, this is a significant transparency gap.

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 focused sentence with no filler. It front-loads the core action and resource, making it easy to parse quickly.

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?

Although the tool has only one parameter, that parameter is undocumented and the behavioral side effects are missing. The description also provides no routing information relative to the many import/material sibling tools, leaving an agent without enough context to confidently select and invoke this tool correctly.

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 0%, and the description does not explain path_name or its expected format. The only useful clue is that the file is an ArmorPaint .arm material library, but the agent still lacks guidance on whether the path is absolute, relative, or must include a specific extension.

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 'Import', the resource (an ArmorPaint .arm material library), and the destination (current project). This also distinguishes it from sibling tools like armorpaint_import_mesh, armorpaint_import_texture, and armorpaint_import_mask, which target different resource types.

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 intended usage is implied: use this tool when you need to load a .arm material library into the project. However, there is no explicit guidance about when not to use it or which alternative should be preferred, especially given the large number of closely related import and material tools.

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