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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds value beyond that by disclosing the return contents (Markdown body, header fields, sketches) and a downstream workflow dependency, though it says nothing about pagination, size limits, or missing-page behavior.

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?

One front-loaded sentence that names the resource and then the payload, with the napkin hint appended as a useful aside. Slightly dense but 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 no output schema, the description usefully compensates by listing the returned contents, and annotations cover the safety profile. Remaining gaps (error/not-found behavior, pagination of attached sketches) are minor for a single-resource fetch.

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%, and the schema itself documents both pageId (with its source, compass_pages_list) and the workspace slug rules. The description only restates 'by id', so it adds essentially nothing over the structured fields — baseline 3.

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 ('Fetches one Compass page by id') and enumerates the payload ('full Markdown body, header fields, and any attached Napkin sketches'), clearly distinguishing it from the sibling list/search/update tools.

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 cross-tool routing: view an attached sketch's actual drawing with napkin_boards_view (its boardId) before discussing it. However, it never states when to prefer this over compass_pages_list or compass_pages_search, so guidance is contextual rather than complete.

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