Get Notion page

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

No annotations exist, but the description correctly identifies the tool as a read operation. It mentions a prerequisite for successful invocation. However, it does not disclose other behavioral traits like rate limits, error responses, or what happens if the prerequisite is not met.

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 concise with two sentences, the first stating the core functionality and the second providing necessary usage context. 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 tool with one parameter and no output schema, the description adequately covers the purpose and a key prerequisite. It lacks details on return value or error scenarios, but remains largely complete for a read operation.

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?

The input schema already has 100% coverage with a description for the 'page' parameter. The tool description essentially restates that the parameter is a Notion page URL or ID, adding no new semantic information 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?

The description clearly states it reads a Notion page's content as markdown, with a specific verb and resource. It distinguishes itself from the sibling tool 'notion_search' which is for searching, not reading a specific 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 by including a prerequisite (page must be shared with integration). It implies usage for reading specific pages but does not explicitly state when not to use it or name alternatives, though sibling tools offer contrast.

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