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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower. The description adds real value by documenting the pagination contract ("If next_cursor is not null, call again with cursor=next_cursor") and the shape of returned records, which matters since there is no output schema. It doesn't mention that visitor_name is unnecessary for reads, which is left to the schema.

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 the resource and returned fields, then use cases, then the pagination instruction. Nothing is redundant or padded.

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 paged read-only listing tool with no output schema, the description covers what comes back, why to call it, and how to continue paginating. All read-path information an agent needs to invoke it correctly is present.

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 description coverage is 100%, so limit, cursor, category, min_rarity and visitor_name are already documented. The description reinforces the cursor loop and the rarity concept (poco_usado 1-5) but adds no filtering semantics, defaults, or format detail beyond the schema.

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?

"List the Atlas of visual styles, one page at a time" gives a specific verb and resource, and the field enumeration (id, name, category, era, origin, poco_usado, palette) makes the scope concrete. It is clearly distinguishable from singular siblings like get_style and from random_style.

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 names two concrete use cases (breaking a creative block, finding rarely used styles) and points to get_style for opening a single style. It stops short of contrasting with random_style or explaining when to use the category/min_rarity filters versus the full listing.

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