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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered upstream. The description still adds non-obvious behavior: the hop does not follow redirects, the ring wraps around, non-active members are excluded, and 'nothing is recorded about who asked' (a privacy guarantee). That is real added context, though it says nothing about the shape or size of the returned payload. With annotations carrying the safety burden, a 4 would be defensible; the missing return-shape detail caps it at 3-4, scored here as 4 given the amount of genuinely new behavioral information.

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-loaded with the core behavior and free of filler; every clause (no redirect, wrap-around, skipped members, no logging) carries information. The first sentence is long and semicolon-chained, which makes it slightly harder to scan than a shorter opening would, 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?

For a three-parameter read with full schema coverage and rich annotations, the description covers selection semantics, edge cases (pending/inactive, wrap-around) and privacy. With no output schema, the one gap is that it never indicates what the returned member record contains (URL only, or name/slug too), leaving the agent to discover the return shape by 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% and the enum on direction is self-explanatory, so the baseline is 3. The description goes further by mapping the prose ('the site after or before `from`') onto the next/previous/random enum values and clarifying that omitting `from` selects a random active member rather than erroring — meaning not present in the schema text.

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 verb and resource ('which member a hop lands on, without following a redirect') and immediately frames it against the obvious alternative behavior (following the redirect) and against get_ring, which lists the members this tool skips. An agent can tell it apart from the sibling listing tools without opening any 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?

Gives concrete usage conditions: omit `from` to get a random active member, direction defaults to next, and pending/inactive members are skipped here but enumerated by get_ring. It stops short of an explicit 'use this instead of X when Y' routing statement, but the conditions for each mode are clear.

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