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

No annotations are provided, so the description carries the full burden. 'Get' implies a read-only operation, but nothing confirms it, and there is no disclosure of what 'detailed information' actually contains, whether it is expensive, or whether the workspace/edit hierarchy must exist first.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity reflects under-specification as much as economy.

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, no annotations, and three required identifiers, the description is only minimally sufficient. It never explains the return shape or the containment relationship among workspaceId, editId, and sceneId, but the fully-covered schema keeps it viable.

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 all three required parameters are documented in the schema (though only tautologically, e.g. 'The scene ID'). The description adds no scoping detail such as the workspace→edit→scene containment, so baseline 3 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?

States a specific verb ('Get') and resource ('a specific scene') plus the scope of the payload ('detailed information'), so an agent knows this is a single-entity read. It does not, however, distinguish itself from siblings like list_scenes or get_edit_full, leaving the boundary implicit.

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?

There is no guidance on when to call this versus list_scenes, get_edit, or get_shot, and no prerequisites are stated. The only usable signal is the singular 'specific scene', which the agent must infer means 'after you already have a sceneId'.

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