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

Annotations already declare openWorldHint=true, readOnlyHint=false, idempotentHint=false, so the safety profile is largely covered by structured data. The description adds the token-savings range and the lean-feed caveat, but does not explain why a 'read' is flagged non-read-only (cost/charging) or disclose the cost mechanism the schema references via max_sats.

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 tightly packed sentences with zero filler, and the core purpose is front-loaded before the usage caveat. Every phrase carries information.

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?

With an output schema present, return format need not be explained, and both params are schema-documented. The description covers purpose and a usage heuristic adequately; the only gap is the unexplained cost/read-only nuance, which is minor given the rich schema and 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?

Schema description coverage is 100%, so both parameters (url, max_sats) are fully documented in the schema itself. The description adds no syntax, format, or cost detail beyond that, so the baseline 3 is appropriate.

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 the resource (RSS/Atom/JSON feed) and the output form (compact items), which is more than a restated title. The verb is implicit ('read feed') but the intent is unambiguous. It doesn't explicitly differentiate itself from siblings like read_webpage or page_metadata, 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?

Provides a conditional heuristic ('on lean feeds skip unless you cannot parse XML') plus a benefit rationale ('Saves 27-81%'). However, it never names an alternative tool to use instead when skipping, so the guidance is implied rather than a clear when/when-not/alternative chain.

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