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

Annotations already declare readOnly/idempotent/closed-world, so safety is covered; the description adds genuinely new behavioral context beyond them — the two call modes (no-arg = catalog list, with-arg = full instructions plus a reference-file list readable via popcraft_get_workflow_bundle_file) and the sequencing/ownership contract ('the workflow owns the production recipe — model choices, reference discipline, credit-cost preview, and QA'). It stops short of describing output format, but the load-first contract is the key trait.

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?

Front-loaded with the mechanics (list vs. load) before the routing rules, which is good. However, the second half is one sprawling multi-clause sentence enumerating scenarios and a long H3 clause; nearly every clause routes a real scenario, but the density and run-on structure hurt scannability, so it is efficient in content yet poor in form.

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?

Covers both invocation modes, the companion tool for reference files, the precedence relative to generation tools, and the ownership of the production recipe. For a single-parameter guidance tool with no output schema, nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the single `workflow` param is already fully described in the schema (name from catalog, omit to list). The description's parallel explanation ('Call with { workflow } to load...') adds corroboration and links the parameter to its effect, but no new syntax or constraint beyond the schema. Baseline 3 is appropriate.

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 ('Discover and load Popcraft's multi-step production workflows') and immediately defines what a workflow is ('a bundled instruction set that orchestrates the popcraft_* tools into a finished deliverable'). It is clearly distinguishable from the popcraft_generate_* siblings it directs the agent away from.

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?

Gives explicit when-to-use conditions (UGC ad, vertical TikTok/Reels ad, thumbnail/cover, voiceover, Hailuo 3 non-trivial jobs), names the alternatives it takes precedence over (popcraft_generate_image/video/audio directly), and even cites the specific failure trigger ('voice came back sounding robotic, flat or rushed'). The precedence rule 'load BEFORE calling...' is unambiguous.

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