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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable behavioral context beyond that: it reveals the local cache dependency, that partial title matches are accepted, and that the tool explicitly reports when content is missing from cache. This gives the agent transparency about limitations and side effects (none) and mitigates false expectations.

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 only three sentences, with the primary action and output in the first sentence. It is front-loaded, and every sentence provides useful information without redundancy. No waste 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?

The tool is simple (2 params, existing output schema, strong annotations). The description covers the tool's purpose, input flexibility, cache limitations, and remediation steps. Given that an output schema exists, there is no need to describe return values. It is complete for an agent to select and invoke correctly, and it differentiates from siblings through the cache emphasis.

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 the schema already documents both 'page' (id or title, partial, case-insensitive) and 'max_blocks' (default 300, max 1000). The description adds no new parameter-level detail beyond rephrasing the page parameter, so it does not elevate beyond the baseline. It does mention 'partial match,' but that is already present in the schema.

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 clearly states the tool 'Reads a Notion page from the local cache and returns its content as markdown.' It specifies the resource (Notion page), the action (reads), and the output format (markdown). It also distinguishes from siblings by emphasizing 'local cache' and listing content types (headings, lists, to-dos, code, files, subpage links), which separates it from notion_read_database and notion_open_page.

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 provides clear context: this tool reads from local cache, implying that for live or uncached content, alternatives may be needed. It explicitly states the fallback behavior ('open the page in Notion or mark it Available offline') when content isn't cached. However, it does not explicitly name alternative sibling tools or state when not to use it, so it stops short of a 5.

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