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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful return-shape information that no output schema supplies: each site comes back with a one-line description and a link, and the enumerated catalogue tells the agent what coverage to expect.

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?

Two sentences, front-loaded with the verb and resource, with the parenthetical catalogue placed before the usage instruction. The site enumeration is long but does real work by signaling scope; nothing else is wasted.

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 zero-parameter read-only listing tool with no output schema, the description covers what the tool returns and when to call it. Ordering, pagination and exact response fields are unspecified, but the catalogue is small enough that this is a minor gap.

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 are zero parameters, so there is nothing for the description to clarify beyond what the empty schema already conveys; baseline for a 0-param tool 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?

States a specific verb and resource ('List every slopped.site site') and enumerates the concrete scope (main gallery plus Scroll, Games, Learn, the Slopwright, Backrooms, codex, Meinong's jungle, GeoCities), which lets an agent distinguish it from siblings like get_artwork or search_world 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?

Gives an explicit trigger condition: 'Use when someone asks what is on slopped.site or where to find something.' It does not name an alternative tool or state when not to use it, so routing when a specific site/artwork is already known is left to inference.

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