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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior. The description adds useful context beyond that: counts are anonymous, there are week and all-time windows, and the response includes names, ids, links and reasons or counts. It does not disclose rate limits or caching, but the important behavioral surface is covered.

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?

The description is a single dense sentence that front-loads the resource and the two modes. Parenthetical details are efficient, though the clause structure is slightly packed. Almost every phrase earns its place by distinguishing modes or listing return fields.

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 appropriately explains that results include names, ids, links, reasons or counts. For a four-parameter read-only list tool, this covers what an agent needs to call it, aside from explicit sibling differentiation and how 'section' applies per mode.

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 75%, with the 'list' and 'window' parameters already described in the schema. The description clarifies the meaning of both modes, including what picks contain and what most-saved counts represent, but adds little for 'limit' or for how 'section' interacts with 'list' and 'window'. Baseline 3 is appropriate when the schema does most of the parameter work.

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 states a specific verb and resource: 'Read top.slopped.site' and distinguishes two modes, curated picks and the most-saved board. It explains the content of each mode with concrete details like 'one-line reason' and 'counted anonymously'. It does not clearly differentiate from the sibling 'of_the_day', which likely overlaps with 'this week’s pick'.

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?

The description gives clear usage context with quoted example questions: “what’s good here” or “what do people like”. It does not name alternatives or exclusions, such as when to use 'of_the_day' or 'list_sites' instead. Clear context but no sibling routing, so it falls short of a 5.

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