readNotionPage

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only says 'Retrieves the content,' which implies read-only but does not state whether the operation is safe, what happens on errors, whether it behaves differently for different formats, or any other behavioral traits. No side effects or constraints are disclosed.

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 a single concise sentence that is front-loaded with the action and resource. Every word adds value; it is not over-specified or verbose.

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 relatively simple, and the schema covers parameters, but there is no output schema, so the description should ideally clarify what 'content' means or what return value to expect. The description gives only a high-level overview and does not mention return structure or edge cases, leaving some gaps for a tool without annotations or output schema.

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 describes both parameters comprehensively (100% coverage), so the baseline is 3. The description adds a minor hint that the output format is controlled by the 'format' parameter ('in the specified format'), but it does not provide additional meaning beyond the schema's own descriptions.

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 action ('Retrieves the content') and the resource ('a Notion page'), and mentions the format parameter, distinguishing it from sibling tools like listNotionPages and queryNotionDatabase. The verb and resource are specific and unambiguous.

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 implies usage for reading a single page's content but does not explicitly state when to use this over alternatives, nor does it provide exclusions or mention of sibling tools. No guidance on when to choose this tool over listNotionPages or queryNotionDatabase is given.

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