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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful context that the call is free, plus a sketch of the returned payload (title, url, metadata, start/end seconds, length) even though an output schema exists. Minor redundancy in restating 'read only' but no misrepresentation.

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?

Front-loaded with the when-to-use clause, then id format, then returns, then a compact 'Not for:' routing list. Every line adds value; the parallel sibling list makes the boundaries scannable in one pass.

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 single-parameter read tool with annotations and an output schema, the description supplies everything remaining: trigger condition, id syntax, return shape, and sibling routing. There is no gap an agent would need to guess at before calling.

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% and the schema only says 'Id: string', so the description carries the full burden — and it does, giving both the provenance ('the id from a search result') and concrete format examples ('projects:abc123', 'library:abc123'). That is exactly the information an agent needs to construct a valid call.

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 — fetching the details of one project or clip — and ties it to the search workflow that produces the id. An agent can immediately tell this apart from list_projects, list_clips, get_download_link and explain_clips.

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?

Explicitly names the triggering condition (user wants details of an item that search found) and then enumerates four exclusions with the sibling that handles each: get_download_link, list_projects, list_clips, explain_clips. Nothing is left to inference.

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