resource_export_mesh_library

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

With no annotations, the description carries the full burden. It explains that the tool creates a file (output_path) and optionally filters items. However, it doesn't disclose potential side effects like overwriting existing files, error conditions, or permissions needed.

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 with a clear front-loaded action, a brief category label (though not essential), and a well-structured parameter list. Every line adds value without redundancy or fluff.

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?

Given that an output schema exists, the description need not explain return values. It covers the core functionality and all parameters. Missing are potential error conditions and prerequisites (e.g., Godot project existence), but the description is largely sufficient for a straightforward export tool.

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 has 0% description coverage, so the description must compensate. It does so by providing clear explanations for all four parameters, including the optional mesh_item_names default behavior. This adds significant value beyond the schema's title-only properties.

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 'Export a scene as a MeshLibrary resource' with specific file types (.tscn to .res). This is a distinct action not shared with any sibling tool, making it easy for an agent to identify its purpose.

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 implies when to use this tool (when a MeshLibrary needs to be created from a scene) but does not provide explicit guidance on alternatives or prerequisites. No mention of when not to use it or how it differs from other resource export tools.

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