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

Goes well past the readOnlyHint/openWorldHint annotations: it discloses the per-item 300-character summary truncation, newest-first ordering, a hard cap of 50 items, and the cost model ($0.002 USDC per successful call via x402 on Base, Solana or Arc, failures not charged). Pricing and truncation are exactly the kind of facts an agent needs before calling an open-world billed tool.

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 what the tool returns, then adds the date filter and the payment terms; every clause carries information. The first sentence is long and parenthetical-laden, but nothing is redundant.

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 field-level return detail is bonus rather than obligation, and the description still names the payload shape. Cost, ordering, caps, date semantics, and the accepted input (feed URL or advertising page) are all covered, leaving no material gap for a 3-parameter read tool.

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 the schema already documents url, limit (1-50, default 20) and since with an example. The description restates the since semantics and the max-50 cap without adding new format or syntax detail, so 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 the resource precisely: items of an RSS, Atom or RDF feed, and also the auto-discovered feed a web page advertises, plus the returned fields and ordering. That is enough to separate it from page-reading siblings like read or extract, though it never names an alternative explicitly and the verb is left implicit ('Items of...').

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 explicit when-to-use or when-not-to-use guidance, and no sibling (e.g. sitemap, links, read) is named as the alternative. Usage is implied by the resource description and by the note that 'since keeps items published on or after a date', which is enough for an agent but requires inference.

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