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

Annotations already declare readOnlyHint and idempotentHint, but the description adds real behavioral detail beyond them: no pagination, newest-first ordering, offline pages included (live: false), deleted pages excluded. That inclusion/exclusion rule is the kind of information an agent cannot get from the annotations or schema.

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 dense paragraph with no filler: scope and ordering first, then the inline response shape, then read-only confirmation, then usage routing. The embedded schema sketch is compact and earns its space since no output schema exists.

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 one-parameter list tool with no output schema, everything needed is present: the return fields are enumerated inline, paging is ruled out, and inclusion/exclusion of offline and deleted pages is stated. Nothing an agent needs to call this correctly is missing.

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 the q parameter's case-insensitive title/content search is already documented; the baseline would be 3. The description adds a decision rule (pass q to search rather than scanning the full list) and clarifies that omitting q lists everything, giving it modest added value over 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?

States a specific verb and resource (list every page in the maker's space), plus ordering (newest first), paging behavior (none), and even the exact return shape. It is immediately distinguishable from get_page, update_page, and the other siblings.

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?

Explicitly names the when: resolving a page_id before update_page / get_page / unpublish_page / delete_page, and reusing an existing project name. It also gives the alternative path (pass q instead of scanning) and the escalation (use get_page when you need one page's HTML).

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