notion_get_page_markdown

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

With no annotations, the description must disclose behavioral traits. It fails to mention what arguments are needed (e.g., page ID), what the tool returns (presumably markdown), error handling, or any side effects. The routing detail is irrelevant to tool behavior.

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 wastes sentences on routing details that do not help the agent understand tool functionality. The first sentence is redundant with the tool name. Useful information is absent.

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 single-parameter tool with an output schema (unseen), the description should at least state that it fetches page markdown. It provides no complete context, leaving the agent unable to use the tool effectively.

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 has 0% description coverage. The description does not clarify the expected structure of the 'arguments' JSON string, which is critical since it's the only parameter. The agent is left guessing what keys like 'page_id' are required.

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 states 'Notion connector operation get_page_markdown' which is essentially a tautology of the name. It does not explicitly state that the tool retrieves the markdown content of a Notion page, leaving the agent to infer from the name alone.

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?

No guidance is provided on when to use this tool versus other Notion tools (e.g., notion_get_page, notion_query_database). The description lacks any context about suitable scenarios, prerequisites, or alternatives.

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