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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds meaningful context beyond those hints: the tool returns an already-existing artifact page and does not refresh or transform data, so the agent knows not to expect fresh computation or side effects.

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 with no filler. The core instruction ('retrieve another page') is front-loaded, and the negative constraints are stated efficiently.

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 pagination tool with full schema coverage and an output schema, the description is complete. It explains the exact purpose, what not to expect, and how to call it correctly; the schema covers parameter formats and valid ranges.

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 the schema already documents offset, brand_id, and artifact_id. The description reinforces copying artifact_id and next_offset, but adds no materially new parameter semantics beyond what the schema provides.

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 a specific verb ('retrieve') and resource ('another page of an existing artifact'), and clarifies what the tool does not do ('filter, aggregate, transform, or refresh data'), which separates it from sibling tools like fetch_data and transform.

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 phrase 'Use only to retrieve another page' clearly states when the tool is appropriate, and 'does not filter, aggregate, transform, or refresh data' excludes common misuse. It does not explicitly name alternative tools for initial fetching or transformation, but the intended usage is unmistakable.

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