well-007-rss-to-markdown

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

Adds substantial behavior beyond the annotations: per-call cost ($0.005 USDC via x402), body cap (1 MB), ~10s timeout, max 5 redirects, and an explicit no-storage/no-warranty statement. The read-only, idempotent, open-world profile from annotations is reinforced and enriched rather than merely repeated.

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 the core purpose, then packs constraints, limits, and the return shape into compact sentences with no redundant filler. The warranty sentence is slightly boilerplate but does carry relevant risk 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?

Despite having no output schema, the description enumerates the returned JSON keys (url, final_url, format, items, markdown, item_count, warnings), so an agent knows exactly what comes back. Pricing, security posture, and limits make it fully self-sufficient.

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 are already documented in the schema. The description restates the max_items default (20) and cap (50) and the URL restrictions but adds no syntax or format detail beyond the schema, making a baseline 3 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 a precise verb+resource pair: converting a public HTTPS RSS 2.0 or Atom feed URL into tidy markdown. The accepted input format and output artifact are both named, so there is no ambiguity about what the tool produces.

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 clear invocation context and hard exclusions — https only, with http/file/data/localhost/private IPs rejected — plus pricing and caps that affect when to call it. It stops short of a 5 only because there are no sibling tools or alternatives to route between.

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