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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds real behavioral context: the ordering (newest first), the fields returned, and the phase taxonomy used for filtering. It stops short of pagination/limit behavior and what includeRemoved actually means.

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 compact sentences, scope and ordering front-loaded, filter semantics second. No filler or restatement of the title.

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 read-only list tool with no output schema, the description does most of the work: what is returned, in what order, and how states/phases can be filtered. The main omissions are pagination/limit behavior and the semantics of includeRemoved (soft-deleted records?).

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 only 33%, so the description must compensate. It does for 'state', enumerating the phase values (storyboard, video, review, music, done, attention) and the 'action' shorthand, which is useful. But 'limit' and 'includeRemoved' get no treatment in either schema or description, leaving that half of the surface underspecified.

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 the resource and scope precisely ('All productions of this account'), plus ordering (newest first) and returned fields (state, next step, readiness flags). It is clearly distinguishable from get_production by scope, though it never names that sibling explicitly.

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?

The description explains filter usage well, including the special 'action' value for 'everything waiting on a decision', which is genuine guidance. However, it gives no when-to-use/when-not guidance relative to siblings like get_production or list_media, and no prerequisites or exclusions.

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