aseprite_run_pipeline

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

No annotations are provided, so the description bears full behavioral burden. It discloses the output layout (files grouped into /output/<folderName>/) which is useful, but says nothing about whether the pipeline overwrites existing folders, how long it takes, whether it can fail partway, whether it costs model calls, or what happens to openInGui. For a heavy multi-stage orchestrator with zero annotation coverage, this is a significant 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?

Two tight sentences: purpose and stage names first, then output location. No filler, well front-loaded.

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?

For an 8-parameter orchestrator with no annotations and no output schema, the description covers purpose and output folder but omits failure behavior, overwrite semantics, runtime expectations, and how outputs relate to sibling inspect/export tools. Adequate but leaves real operational gaps.

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 the schema already documents every parameter including defaults and examples. The description adds the output-path semantics tied to targetFolder/folderName, which is beyond the schema. Baseline would be 3, lifted slightly by that added folder-naming context.

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?

States a specific verb+resource: runs a named 3-stage multi-agent asset pipeline and lists the stages. It clearly distinguishes itself from atomic siblings like create_sprite or draw_pixels by being the orchestrating pipeline. It doesn't explicitly name sibling alternatives, but the scope is unambiguous.

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?

Implies usage (generate a full game asset from a prompt via a multi-agent flow), but gives no explicit when-to-use vs when-not, no comparison to running individual stage tools like aseprite_analyze_style first, and no note on cost/time of running the full pipeline.

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