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

Annotations cover the safety profile (readOnlyHint=false, openWorldHint=true, non-idempotent, non-destructive), and the description adds substantial extra context: a 7-credit cost with a stated discount rationale, the upstream chain it wraps, and importantly the non-obvious caveat that when quality.level is not "full" or verdict is NEEDS_MORE_DATA/NO_GO the output is not shippable. It stops short of describing auth/prerequisites, so it is strong but not exhaustive.

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 outcome is front-loaded in the first clause ("Turn a brand brief ... into a one-page creative blueprint") and every subsequent sentence adds distinct information (trigger, chain, cost, return shape, caveat). It is dense and the first sentence runs long, but there is little filler.

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 a 7-parameter, high-complexity orchestration tool, the description covers trigger conditions, cost, upstream dependencies, the shape of the result, and the interpretation caveat for degraded verdicts. An output schema exists, yet the description still summarizes return fields in a way that helps an agent decide whether the result is usable.

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%, including the enum mappings, region threading, platform behavior, creator_handle voice matching, and how deadline_hours affects trend scoring — so the schema carries the parameter burden. The description adds only high-level phrasing ("trend-velocity check", "creator context") that does not extend beyond the field-level docs, which is the expected baseline when coverage is complete.

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 transformation (brand brief → one-page creative blueprint) and enumerates exactly what the artifact contains (hook, template, hashtag combo, trend-velocity check, shoot instructions). It also distinguishes itself from siblings by naming the chain it bundles (find_viral_template + trend_pulse + score_hook + predict_virality) and explaining they are exposed as one tool.

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 an explicit triggering scenario ("product arrived, need content in 48 hours") and the persona/condition (manager needs a defensible direction with no research time). It also implicitly routes agents away from manually stitching the four upstream sibling tools.

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