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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavior beyond them: results are paged, reflect the database's current stored state rather than a fresh query, and each match carries a 'new' marker tied to whether the account has seen it (implying interaction with mark_changes_seen). It does not explain what happens past the last page or the page size limit, which remain implied.

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 that puts the resource first and packs pagination and the 'new' marker into the same clause with no filler. It is dense but not padded; a slight readability cost from the many comma-separated clauses.

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?

With no output schema, the description carries the burden of describing returns; it covers paging and the 'new' flag but says nothing about the shape of a match record or how to tell when the last page is reached. Adequate for invocation, thin for interpreting results.

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 folder_id, item_id, and page are already fully documented by the schema. The description's 'a page at a time' only restates the paging parameter and adds no format or ordering semantics 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?

The description names a specific resource (every match of a saved search in a folder) and its retrieval mode (paged, snapshot of stored results). It implicitly separates itself from live `search`-family tools via 'as the database holds them now', but never names a sibling explicitly.

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?

There is no explicit when-to-use/when-not guidance or named alternative; the agent must infer that this reads persisted search results rather than running a new search. The snapshot phrasing hints at the distinction from `search`, and the schema's 'from get_folder' pointer supplies the prerequisite, but the description itself provides no routing.

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