Inspect Project Item Av Metadata

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds useful scope detail (documented effective vs original color space, LUT IDs, overrides, audio channel shape), but does not explain what 'documented' values mean when absent or how missing metadata is represented.

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 dense sentence with the verb and object front-loaded and the inspected fields listed compactly. No filler or redundancy.

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 an output schema present, the description need not explain return values, and annotations cover safety. The field enumeration plus the single documented parameter make the definition sufficient to call correctly; only the missing routing guidance against overlapping inspection tools is a gap.

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?

Only one parameter (item_id), and schema description coverage is 100% — the schema already explains it accepts a node ID or exact name. The description adds nothing about item_id, so the 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 ('Inspect') and resource ('a project item's ... metadata') and enumerates the exact fields surfaced: effective/original color space, LUT IDs, color-space overrides, and audio channel shape. This distinguishes it from generic readers like get_clip_properties or get_color_space, though it does not name those siblings 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?

No when-to-use or when-not-to-use guidance. Given overlapping siblings such as inspect_sequence_av_settings, get_color_space, get_clip_properties, and get_av_feature_support, the agent must infer on its own whether this item-level AV metadata inspection is the right call versus those alternatives.

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