get_page_content

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

No annotations are provided, so the description must disclose behavioral details. It only says 'Get...', which generically implies a read operation, but does not state that it is non-destructive, what the return format is, or any limitations (e.g., whether it returns only top-level blocks). This is insufficient for a read tool with no output schema.

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 with no filler. It is front-loaded with the verb 'Get', but its brevity comes at the cost of helpfulness, which is penalized in other dimensions.

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?

Given the tool has no annotations and no output schema, the description should clarify the return value and read-only nature. It does not mention what the output looks like (e.g., an array of block objects) or any error conditions. The description is adequate for a very simple tool but lacks enough context to be fully complete.

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 schema already documents 'page_id' with full coverage, so the baseline is 3. The description adds minimal context by implying the page_id identifies the page whose content is retrieved, but it does not add format, constraints, or usage details beyond 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 'Get the content/blocks of a Notion page' with a specific verb and resource. However, it does not explicitly differentiate from the sibling 'get_page' tool, which may retrieve page metadata instead.

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 it should be used when you need the content/blocks of a page, but it does not provide explicit guidance on when to use this tool versus alternatives like 'get_page' or 'search_pages'. No exclusions or alternative references are mentioned.

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