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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful scope context by stating it does not copy wording, logos or footage into the program. However, it never explains the notable idempotentHint=false on a read-only tool (i.e., results may vary between calls) or whether the analysis is costly/slow, which are the traits an agent would most want flagged.

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 sentences, front-loaded with the core action, and the second sentence earns its place by fencing off the common misconception that reference analysis means copying source material. No filler or restated 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?

With only two parameters, no nested objects, and no output schema, the description covers the conceptual job adequately, including the negative scope boundary. It falls short on prerequisites (uploaded asset, active project) and on what the mapping result looks like or how the agent should consume it.

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 50%: project_id carries a schema description warning that the navigation pointer does not select the target, while asset_key is bare with no type-level explanation. The description mentions neither parameter, so it does nothing to clarify what an asset_key is or where it comes from (presumably upload_start), leaving the coverage gap unaddressed.

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 and resource ('Analyzes the sequence of visual-device classes in an uploaded reference') and adds a precise scope limit ('maps those classes to moments in the current edit') that separates it from additive siblings like add_device_stage or add_overlay. It does not name a sibling alternative outright, so the differentiation is inferential rather than explicit.

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?

No guidance on when to choose this over analyze_music, compare_uploaded_media, or suggest_devices, and no stated prerequisites such as requiring the reference to be uploaded first via upload_start or a project already open. Usage must be inferred entirely from the phrase 'an uploaded reference'.

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