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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the body is truncated to the first 4,000 characters by default, and include_html switches to the full HTML body. It does not mention pagination or rate limits, but the truncation semantics are the important disclosure here.

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?

Two sentences, front-loaded with the resource and its returned contents, then a short pointer to the sibling for id lookup. The long enumeration of return fields is dense but each item earns its place by telling the agent what it can extract from a single call.

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?

Although an output schema exists (so return values needn't be spelled out), the description still gives a useful preview of payload contents plus the truncation rule, and it covers the id-sourcing prerequisite. Nothing an agent needs to call this correctly is missing.

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 50% – include_html is documented in the schema, while article_id is not. The description compensates by explaining what include_html changes (excerpt vs. full HTML) and by directing the agent to list_articles for the id, so both parameters have usable meaning even though the id's format is only conveyed by the schema's uuid pattern.

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?

The description names a specific verb (read) and resource (one article in this workspace) and enumerates exactly what is returned: metadata, status, meta description, text excerpt, cited sources, and JSON-LD structured data. It also names the sibling list_articles as the discovery path, so an agent can distinguish it from list tools without opening a 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?

It explicitly routes the agent to list_articles to obtain the required article_id, which is the key prerequisite for invoking this tool. It does not state when to prefer a different retrieval path (e.g. search_rankwise_content) or any exclusions, so it stops short of a full when/when-not treatment.

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