export_mesh_library

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

With no annotations, the description discloses key behaviors: silent file overwrite, error on missing meshes, and subset export. However, it does not explicitly state that the original scene remains unmodified, which is a reasonable inference but could be clearer for full 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?

The description is concise at 4 sentences, with the first two conveying purpose and usage context immediately. Each sentence adds necessary information without redundancy or fluff, making it easy for an agent 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?

The description covers purpose, usage, prerequisites, parameter behavior, output, and error handling. For a tool with no output schema and moderate complexity, this is largely complete, though a slight improvement would be specifying that meshItemNames correspond to MeshInstance3D node names.

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?

Input schema has 100% coverage, so baseline is 3. The description adds value by clarifying the constraint that the scene must contain MeshInstance3D children (for scenePath) and specifying silent overwrite for outputPath, going beyond the schema 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?

The description clearly states the tool's purpose with a specific verb ('Export') and resource ('MeshInstance3D nodes as a MeshLibrary .res file'). It distinguishes from sibling tools by specifying its use for grid-based 3D levels and excluding 2D or general scene work.

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 description provides explicit usage context: 'Use this when authoring tile palettes for grid-based 3D levels; ignore for 2D or general scene work.' It also lists prerequisites (scene must contain MeshInstance3D children) and explains optional parameter behavior, helping the agent decide when to invoke this tool.

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