notion_pages_retrieve_markdown

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotency are covered. The description adds real value beyond them: server-side rendering by Notion to Markdown and the cost/efficiency characteristic of a single call versus recursive block listing. It does not mention large-page truncation or auth requirements.

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?

Two sentences, no filler, with the core purpose front-loaded and the sibling comparison immediately after. Every clause carries information an agent can act on.

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 two-parameter read tool with no output schema, the description conveys the return format (full page content as Markdown) and the key routing decision. Only minor gaps remain, such as behavior on very large pages or whether transcripts are excluded by default.

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 both `pageId` and `includeTranscript` are already documented in the schema, and the description adds no syntax or default information beyond that. Baseline 3 applies when the schema does the heavy lifting.

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 ('Get a page's whole content as Markdown') plus the rendering source ('rendered by Notion'). It explicitly contrasts with the sibling `blocks_children_list`, so an agent can pick it without opening the schema.

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?

Names an alternative (`blocks_children_list`) and the condition that favors this tool ('One call instead of recursing'), plus a usage cue ('a page you only need to understand rather than edit'). It stops short of naming the edit-oriented alternative or stating hard exclusions, so it is clear but not fully routing.

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