get_collective_pages

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds important behavioral context: it returns a page tree with landing page and subpages, reports pagination metadata, and explicitly excludes page text. This goes well beyond the annotation data and helps the agent call and interpret the result correctly.

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?

The description is front-loaded and structured into purpose, Args, and Returns sections. Every sentence adds useful information without repetition or 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?

Given that an output schema exists, the description need not explain return values, yet it helpfully summarizes the return shape, pagination, and the absence of page text. It provides everything needed to call the tool correctly and route to get_collective_page for page content.

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 fully carries parameter meaning. It explains collective_id as the numeric ID and points to list_collectives, specifies limit as 1-200 with default 50, and describes offset as pages to skip for pagination with default 0.

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 states a specific verb+resource: "List pages in a collective." It further clarifies scope by saying it returns the page tree including landing page and all subpages, and it differentiates from get_collective_page by pointing there for page text. This is more precise than a generic list tool.

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?

It gives clear usage context by naming list_collectives for finding IDs and get_collective_page for reading page text. However, it does not explicitly compare against sibling listing/search tools like search_collective_pages or list_recent_collective_pages, so the when-not guidance is incomplete.

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