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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is to add behavior — and it does, disclosing newest-first ordering and a 10-per-page page size, which the agent would otherwise have to discover empirically. It doesn't mention what an empty or terminal page looks like, so it stops short of 5.

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?

A single front-loaded sentence with no filler; ordering and page size — the two facts an agent needs — come first.

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 simple two-parameter paginated read with full schema coverage and covering annotations, the description supplies the missing runtime facts (ordering, page size) and no output schema exists to require return-value explanation. Only an explicit statement of how pagination terminates is absent.

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 both the store id and cursor are already documented, and the schema even explains where each value comes from. The description adds only the page size, which is relevant context for the cursor but not meaningful parameter detail beyond the baseline.

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 names the resource (articles on the store blog) and its ordering, which lets an agent recognize this as the paginated listing counterpart to read_blog_post. It is clear but never states an explicit verb or calls out the sibling distinction.

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?

Usage is only implied: the plural listing vs. read_blog_post's single-article read is inferable but never stated, and there is no explicit when-to-use or when-not guidance.

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