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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the safety profile is covered. The description goes beyond them by disclosing the payload shape — verified facts, fidelity findings, QA findings, credits used, recent events, suggested next tool — which tells the agent this is a heavy, aggregate read rather than a stub. It omits error behavior for unknown or deleted IDs.

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?

One front-loaded sentence: the resource is named first, then the contents are listed. Nothing is redundant, and each enumerated item carries information about a distinct section of the response.

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 must preview return values, and it does so thoroughly across every major section of a production. For a one-parameter read tool that is largely sufficient; the only real gap is failure/edge-case behavior for stale IDs.

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?

There is a single parameter and schema coverage is 100%, with the schema itself noting the ID comes from list_productions or create_production. The description adds nothing about the ID beyond that, so the baseline of 3 for high-coverage schemas applies.

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?

"Full detail of one production" gives a specific resource plus an explicit scope qualifier ("one"), which separates it from the list-style sibling list_productions. The enumerated contents (storyboard, videos, music, credits, events) further pin down what "detail" means, though no sibling is named outright.

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 only implied: an agent infers it should call this once it holds a productionId and needs the full picture. There is no explicit when/when-not guidance, no mention of preferring list_productions for browsing or view_storyboard_images for a narrower lookup. The note that the response includes "the suggested next tool" is the one sequencing aid offered.

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