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

Annotations already flag readOnlyHint=true, and the description layers on real operational detail beyond that: a rate limit of 30 pages an hour, web-only text restriction, the failure shape for video links with error_code 'desktop_only' plus a download_url, and a cached flag. That is exactly the kind of context the structured fields cannot carry.

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-loads the purpose, then uses compact Args/Returns blocks so an agent can scan the call contract and return shape quickly. Dense but nearly every clause carries signal; the only wasted motion is restating the 2000-char limit already in the schema.

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?

No output schema exists, so the description supplies the return shape itself (ok, source, url, title, brief with about/facts/audience/tone, excerpt, chars, cached) plus the failure shape. For a single-parameter read tool this is more than sufficient to call it correctly and interpret the result.

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 0%, so the description must carry the param load, and it does: url is an https link to an article or post, max 2000 chars. The max-length detail duplicates the schema's maxLength, so it is a small amount of redundancy rather than pure added meaning, but the accepted content type is genuinely new information.

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?

Names a specific verb and resource (reads a source page into a brief that the video director remixes) and states the downstream consumers by name (script_coach, ai_short_draft). An agent can tell this apart from a plain article reader. The only wrinkle is the phrase 'answers desktop_only', which reads like an error code but collides with a sibling tool of the same name.

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?

Gives a clear operating context: it is free at 30 pages an hour, and the resulting brief should be passed to script_coach or ai_short_draft. It also rules out video links on web. It does not explicitly say when to prefer this over read_article, so the sibling routing is only partially covered.

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