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

With readOnlyHint/idempotentHint already declaring the safety profile, the description still adds real value: it discloses that no credits are consumed, describes the returned node/edge structure, and explains the semantics of isShotPanel, isStarred and defaultNodeId. That is meaningful behavioral context beyond the annotations, though it stops short of describing limits or error/auth conditions.

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?

Purpose and scope are front-loaded, and the following sentences (mediaId/view_media, isShotPanel/isStarred, defaultNodeId, read-only/no credits) each carry distinct information. The opening sentence is a dense run-on with stacked parentheticals, which slightly hurts scannability.

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 tool with no output schema and a nested target object, the description compensates by enumerating what is returned (nodes, prompts, refs, edges, mediaIds) and the meaning of key flags and the default write target. An agent has enough to call it correctly and interpret results without further sources.

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%, and the nested target schema already documents kind, group, id and the shot/story_element/art_direction variants in detail, so the baseline is 3. The description's parameter-adjacent contribution (defaultNodeId's role) actually concerns the response, not the inputs, so it adds little to parameter meaning beyond the schema.

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?

The description uses a concrete verb ('Read') and precisely characterizes the resource: a shot's storyboard/production group, a story element's moodboard/storyboard/production group, or the art direction. This is far more specific than the title, but it never explicitly contrasts itself with database siblings like get_scene or get_project_outline, so it falls short of full sibling differentiation.

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 through output-oriented hints – it tells the agent to reach for view_media to see an image's mediaId, and that defaultNodeId is the write target for add_reference_images/set_prompt. However, it gives no explicit when-to-use vs when-not guidance relative to get_scene or get_project_outline, leaving selection mostly to inference.

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