list_recent_collective_pages

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context by defining what counts as a change ('Changes by anyone count; visits do not'), which directly determines the result ordering.

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?

Purpose is front-loaded, followed by tightly written Args and Returns sections with no filler. The Returns block partially overlaps the existing output schema, but it still earns its place by documenting the collective_id null edge case.

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 and annotations covering the safety profile, the description supplies what is missing: both parameter semantics and the sort/change semantics. It omits any note on pagination or required permissions, but for a read-only list tool nothing critical is absent.

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 0%, so the description must carry the full burden, and it does: 'query' is defined as a title-contains filter with a default of all, and 'limit' is bounded (1-100) with a default of 10. Both parameters gain meaning that the bare schema (only titles and defaults) does not provide.

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 and resource ('List the most recently changed pages') and adds scope and ordering ('across all your collectives, newest first'), which implicitly separates it from siblings like get_collective_pages or search_collective_pages. It never names an alternative sibling explicitly, so it stops short of the top tier.

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?

'Changes by anyone count; visits do not' clarifies the meaning of 'recently changed', which is useful selection context. However, there is no explicit when-to-use-this-vs-another-tool guidance (e.g., versus search_collective_pages or get_collective_pages), leaving usage only implied.

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