Recent Pages

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds behavioral detail the annotations don't carry: result ordering is newest-first and the scope can be a single space or the whole workspace. It stops short of defining the recency window or whether inaccessible pages are filtered.

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 tight sentences. The core behavior and ordering are front-loaded, and the second sentence is a single high-value routing pointer with no filler.

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 an output schema present, the description needn't explain return values, and all three parameters are schema-documented, so an agent can call it correctly. The remaining gap is the undefined meaning of 'recently' (time window and whether edits or creations count), which matters for interpreting the result.

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 limit, cursor, and space_id are already fully documented. The description only reinforces that space_id is optional ('one space or in all spaces') and adds no format or constraint detail beyond the schema, so the baseline of 3 applies.

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 recently updated pages') plus ordering ('newest first') and scope ('one space or in all spaces'). It explicitly distinguishes itself from the closest sibling, list_page_history, so an agent can choose without opening either schema.

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?

Gives an explicit purpose ('to see what changed lately') and names the alternative for the per-page case ('For the changes of one page, use list_page_history'), which is a clear routing rule. It does not contrast with list_pages (all pages, not time-ordered), so the space of alternatives is only partially covered.

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