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

With no annotations provided, the description carries the full burden and does well: it discloses the operation is non-converting (read-only), is free, may run as a long job returning a job_id to poll via get_job, and that result links expire in one hour. These are exactly the operational traits an agent needs. It still doesn't say what happens on an unreachable/unsupported file.

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?

The capability list is front-loaded and the operational notes follow compactly. The only waste is the redundant 'Free. Cost: Free.' duplication, which costs it a point.

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 one-parameter tool with no output schema or annotations, the description covers the return contents, cost, async/polling behavior, and link expiry. The main omission is error behavior for unsupported or inaccessible URLs, which is a minor 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?

Schema description coverage is 100% and the single parameter is fully documented in the schema itself ('Source file: public http(s) link'). The description adds no format or constraint detail beyond that, so the baseline of 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 (read/inspect) and resource (a media file) and enumerates exactly what is extracted: duration, resolution, frame rate, codecs, bitrate, audio tracks, metadata tags. It is clearly a read-only inspection tool, though it does not differentiate itself from the sibling analyze_media, which sounds closely related.

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?

The phrase 'without converting it' implies this is the non-destructive inspection option versus conversion/edit siblings, and 'Free' hints at cost considerations. However, it never states when to prefer this over analyze_media or edit_metadata, so the guidance is only implied.

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