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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real value by disclosing the three return variants (plain, styled, raw links) and the constraint of no script or no images. It does not state rate limits or exact response structure, but it goes meaningfully beyond the annotations.

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?

Information-dense and front-loaded, leading with what the tool produces before the return-variant details. The first sentence is long and clause-heavy, but almost every clause carries actionable detail rather than filler.

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 three-parameter read-only tool with no output schema, the description fully covers inputs' roles, output variants, and safety constraints (no script, no images), leaving nothing an agent needs before calling it.

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 coverage is 100%, so the schema already documents all three params. The description nonetheless adds meaning: it explains that hops are measured from the `site` homepage and that omitting it produces a placeholder, and that rings drive row ordering — semantics not obvious from the field descriptions alone.

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 deliverable: the copy-paste footer HTML a site embeds to show webring membership, with the `<< Ring >> / prev / ring page / next` shape spelled out. It is clearly distinct from siblings like rssamplifier_get_ring or rssamplifier_ring_next, which fetch ring data rather than emit embed code.

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 operating context: rings are slugs taken from list_rings, `site` is the member homepage, and omitting it yields a placeholder. It does not explicitly exclude cases or compare against other ring tools, but the routing pointer to list_rings removes the main ambiguity.

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