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

Annotations already declare openWorldHint=true (external fetch) and idempotentHint=true, and the description corroborates the external-source behavior. However, readOnlyHint=false is unusual for a fetch and the description never explains the side effect this implies (e.g. caching/storing the fetched text) or what happens if the publisher page is unreachable.

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?

One sentence, front-loaded with the action and resource, with the motivating condition trailing as a qualifier. No wasted words.

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 one-param fetch with no output schema, the description conveys the essential behavior and return intent ('full text'). Minor gaps remain around failure modes and the non-read-only side effect flagged by annotations.

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?

The single parameter is fully documented in the schema (article_id: 'The article ID to extract content for'), so the schema does the heavy lifting. The description adds no format, sourcing, or constraint detail beyond what the schema states; baseline 3 applies.

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 ('Fetch'), resource ('full text of an article'), and source ('publisher's original page'), plus the motivating condition ('feeds that publish only an excerpt'). This clearly distinguishes it from the sibling get_article, which presumably returns stored content.

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 trigger condition: use it when the feed only publishes an excerpt. It does not explicitly name get_article as the alternative for when full content is already stored, so the routing is implied rather than spelled out.

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