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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context: it is '$0', and it precisely discloses what `compact=true` omits and how null defaults are represented, going beyond the annotation profile.

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?

It is front-loaded with the core definition, and every clause carries information, but it is delivered as one dense run-on sentence packing output-structure details together. It would be more scannable if split into short points; the length is on the heavy side.

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?

With no output schema, the description carries the full burden of describing return values and does so thoroughly: it lists the referent fields, explains the null/platformDefaults semantics, names the additional catalogues (duration profiles, output formats, budget tiers, writingProfiles), and covers cost and both parameters. An agent has enough to call and interpret it correctly.

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 baseline is 3. The description's parameter content ('locale selects the language', 'compact=true leaves out...') largely restates what the schema already documents, adding only marginal specificity about which catalogues drop out.

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 (list) and resource (creative referents / formats a piece can be produced in) and defines the concept precisely with examples (documentary, explainer, viral short). It also explains the referent id's role ('the value of creative_referent when a piece is created or priced') and enumerates the additional catalogues returned, making it distinguishable from sibling list_* tools.

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?

Usage is implied rather than stated: the note that the referent id is used when a piece is 'created or priced' and that 'production accepts' these duration/format/budget values hints at the workflow, but there is no explicit 'call this before produce/estimate' instruction or named alternative. No when-not guidance is given.

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