export_spritesheet

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'optional frame metadata' but does not explain what that entails (e.g., file formats, side effects like writing files, or whether it modifies the sprite). It also does not state any required state (e.g., frames must exist). This is a significant gap for a tool that produces an output.

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 sentence, which is brief, but it is under-specified rather than appropriately concise. It does not front-load essential usage constraints or parameter explanations. Every word is spent on stating the obvious purpose, leaving no room for the information an agent needs. It is not concise in a way that adds value.

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 the tool's complexity (9 parameters, no annotations, no output schema), the description is grossly incomplete. It does not explain what the output looks like, how the parameters interact, what 'optional frame metadata' means, or any side effects. An agent cannot reliably call this tool correctly based on the description alone.

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%, so the schema provides no parameter descriptions. The description adds zero information about any of the 9 parameters, including critical ones like filename, output_filename, sheet_type, data_format, scale, padding, tag_name, list_tags, and data_filename. The agent is left with only the schema's structural hints, which are insufficient for correct usage.

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 specific action ('Export a spritesheet') and a target ('for Godot'), clearly indicating the tool's primary purpose. It does not explicitly differentiate from siblings like export_frame or build_animation_sheet, but the resource (spritesheet) is distinct enough. It is not a tautology and conveys the core function.

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 given on when to use this tool versus alternatives. It does not mention prerequisites, such as having an active sprite with frames, nor does it explain when to choose export_spritesheet over export_frame, export_tag, or build_animation_sheet. The agent must infer usage from the name and context.

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