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

No annotations are provided, so the description carries the full burden of behavioral transparency. The verb 'List' communicates a read-only operation and the restoration note adds useful context, but the description does not mention pagination, ordering, or what fields are returned. It is honest but minimal.

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 short sentences, with the core purpose front-loaded in the first sentence and a relevant, non-redundant follow-up in the second. There is no padding or unnecessary detail.

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 zero-parameter, no-output-schema read tool, the description is nearly complete: it states the exact object (deleted pages) and the natural follow-up action (restoration). The only omissions are minor operational details like pagination or ordering, which are not strongly implied by the schema.

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?

The input schema has zero parameters and the description does not need to invent parameter-level detail. With no parameters to document, this is effectively a baseline-4 situation; the description correctly avoids irrelevant parameter content.

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 uses a specific verb ('List') and a specific resource ('all deleted pages in the trash'), distinguishing this tool from sibling list_pages, which presumably lists non-deleted pages. It clearly states what the tool does with no ambiguity.

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 description implies when to use this tool (when you need to see deleted pages), but it does not explicitly name alternatives or state when not to use it. The note that deleted pages can be restored hints at a follow-up workflow but never points to restore_page or list_pages.

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