export_mesh_library

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

The description states it exports, which implies file creation, but does not disclose potential side effects (e.g., overwriting), required permissions, or if it's destructive. With no behavioral annotations beyond title, the agent lacks transparency.

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, clear, front-loaded sentence with no unnecessary words. Every word contributes to understanding the tool's function.

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 schema covers parameters, the description lacks important context such as the purpose of the optional 'meshItemNames', expected file formats, or error scenarios. For a tool with no output schema, more behavioral description would help.

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 baseline score is 3. The description does not add any extra meaning beyond what the schema already provides for parameters.

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 uses specific verb ('Export') and resource ('scene as a MeshLibrary resource'), making the purpose immediately clear. It distinguishes from sibling tools like 'export_project' by specifying the output type.

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 on when to use this tool versus alternatives (e.g., other export tools). No mention of prerequisites, when not to use, or context where this tool is appropriate.

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