media_info

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds the meaningful trait that no media is downloaded, but is silent on private/geo-blocked URL failures, authentication, or rate-limit behavior for an open-world network tool.

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 the core constraint ('without downloading') placed early and zero filler; the dash-list efficiently conveys return contents.

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, the description usefully enumerates the returned fields, and annotations cover safety, so an agent knows what it gets back. The main residual gap is the undocumented `playlist` parameter behavior, which matters for correct invocation.

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 0% for both parameters, so the description must compensate and it does not: the `playlist` boolean is never mentioned, leaving unclear whether it expands playlist entries or is required for them. Only the URL's implicit nature is conveyed through the output listing.

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 (YouTube/other URL), enumerates the exact outputs (title, channel, duration, formats, chapters, subtitles, playlist entries), and the 'without downloading' clause separates it from media_youtubeDownload. An agent can distinguish the intent from every sibling without opening the schema.

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?

'Without downloading' clearly implies the inspect-then-download workflow and implicitly routes to media_youtubeDownload for actual fetching, giving strong usage context. It stops short of explicitly naming the alternative or when-not conditions, so it is not a full 5.

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