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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: page size of 50, `limit`/`offset` paging, and the presence of `total` and `nextOffset` in the result. It stops short of describing auth or rate-limit behavior, which the schema carries for `workspace`.

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?

Front-loads what it lists and the workspace scope, then layers filtering, pagination, and sibling routing in three tight sentences. Nothing is padding, and the most decision-relevant routing advice is easy to find.

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?

No output schema exists, but the description discloses the return shape (summaries, total, nextOffset) and points to `compass_pages_get` for full bodies, which is everything an agent needs to page and follow up correctly.

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 every parameter is already documented in the schema, establishing a baseline of 3. The description reinforces the `type` enum and pagination parameters but adds no syntax or format meaning beyond what the schema provides.

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 (lists pages in the active workspace's Compass compendium) plus scope. It explicitly routes to sibling tools (`compass_pages_get` for full bodies, `compass_pages_search` as a better first call), so an agent can differentiate it without opening other schemas.

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 explicit alternatives with conditions: use `compass_pages_get` when you have a page and want the full body, and use `compass_pages_search` when you already know what you're looking for. This is concrete when-to-use guidance, not inference.

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