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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, open-web nature is covered structurally. The description adds that the content is 'public' and that body HTML is 'rich' with 'normalized' paragraphs, which is modest extra context but not deep behavioral disclosure such as rate limits or paywall handling.

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?

It is a single, tightly packed sentence with no wasted words, front-loading the resource identity before the returned content types. The only knock is that it is a noun-phrase fragment rather than a clear action statement.

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?

An output schema exists, so return values need not be explained, and the description still lists the content categories. However, for an open-world fetch tool it omits any caveat about non-Forbes URLs, paywalled content, or failure behavior, leaving it only minimally complete.

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% and the description never mentions the single 'url' parameter, its expected format, or whether it must be a Forbes domain URL. The parameter is self-evident from the name, but the description does not compensate for the schema's lack of documentation.

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 the specific resource (a public Forbes article) and enumerates what it returns (metadata, body HTML, paragraphs, headings, embeds), which lets an agent distinguish it from siblings like forbes_headlines or forbes_author. It is a content list rather than a verb-led statement, and it never explicitly contrasts with those siblings, so it stops short of a 5.

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?

There is no when-to-use guidance, no condition that selects this tool over forbes_headlines or forbes_author, and no note about prerequisites. The agent must infer that this is the article-detail tool purely from the name and resource description.

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