page_list

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

Discloses pagination order (newest first), offset semantics, and limit cap. With no annotations, the description carries full burden; still lacks return format and edge-case behavior.

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 sections: purpose sentence and concise arg list with examples. No superfluous text, front-loaded.

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?

Good coverage of purpose and params, but no output schema or return value description. For a simple pagination tool, it is mostly complete, but return format would strengthen it.

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 has zero descriptions (0% coverage), and the description fully explains all three parameters with examples and constraints, adding significant meaning 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?

Clearly states the tool pages through a list's messages newest first, with specific verb and resource. Distinguishes from siblings like search_list and get_message by focusing on sequential paging.

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?

Implies use for paging through messages but does not explicitly contrast with siblings. No when-not-to-use or alternatives mentioned.

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