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

With no annotations, the description carries the behavioral disclosure burden. It does disclose key behavior: slim metadata is the default, folder_id filters results, and slim=false triggers full details. It does not mention pagination, result limits, ordering, or the exact shape of 'full page details,' which are relevant for a list endpoint without an output 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?

Three short sentences, front-loaded with the core action and default behavior. Every sentence adds information: what is listed, what the default returns, how to filter, and how to opt into the heavier response. No wasted words.

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 simple read-only listing tool with two optional parameters and no output schema, the description covers the default return fields and explains both parameters. It leaves some gaps—full-details response fields, pagination, and behavior when no folder_id is provided—but the essential invocation context is present.

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 baseline is 3, but the description adds meaning beyond the schema. It maps folder_id to 'project' semantics and warns that slim=false should be used 'only if' full details are needed. This gives an agent practical guidance on when and how to use each parameter.

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 opens with a specific verb and resource: 'List pages.' It further clarifies the default response shape (slim metadata with id, title, folder_id, parent_id, tags, type), which helps distinguish this bulk-listing tool from nearby siblings like search_pages or get_page. However, it does not explicitly name or contrast any sibling 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?

The description gives clear parameter-level guidance: 'Use folder_id to filter by project' and 'Use slim=false only if you need full page details.' This implies the tool's main use case but does not explain when to prefer list_pages over search_pages, find_page_by_root_path, or list_folders. There is no when-not-to-use or alternative routing.

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