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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing the shape of the returned document (ordered members with site, feed, status enum-like values, and optional made_by/disclosure) and by noting it is the same document served at /ring/<slug>/openwebring.json, which tells the agent the data is a static, cacheable view.

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?

Three sentences, front-loaded with what is returned, then the alternative-tool routing, then provenance. Every sentence carries information except the trailing 'Served by RSSAmp (https://rssamp.com/mcp)' line, which is boilerplate for this server family.

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?

There is no output schema, so the description must carry the return contract, and it does: member ordering, the per-member fields, and the enumerated status values. Combined with schema-covered parameters and annotations that cover safety, an agent has everything needed to call it correctly.

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?

There is only one parameter and the schema already documents it at 100% coverage ('The ring slug, from list_rings'). The description reinforces the source of the slug, but adds no syntax or format detail beyond what the structured field provides, so the baseline of 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?

The description names a specific verb and resource ('get_ring' → a ring's members in ring order) and enumerates the returned fields: site, feed, status, made_by, disclosure. It also distinguishes itself from rssamplifier_ring_next by stating that ring_next is the tool for following a hop, so an agent can pick between them without opening a schema.

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?

It gives explicit routing guidance: use ring_next to follow a hop rather than computing one from this list, and the slug comes from list_rings. What is missing is a stated boundary against the related embed/JSON-document siblings (e.g. rssamplifier_ring_embed), which would make the choice fully unambiguous.

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