notion_open_page

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states 'opens via deep link' but does not mention prerequisites (Notion installed?), side effects (window focus?), or authorization needs. Significant gaps given the lack of annotations.

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 efficient sentence with no redundant words. It delivers the core message without unnecessary elaboration.

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 description is too brief for a tool with no parameters, no output schema, and no annotations. It fails to explain which page is opened, error conditions, or how the tool interacts with the desktop app. Important context is missing.

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 has zero parameters (baseline 4), but the description introduces ambiguity by stating 'a Notion page' without indicating how the target page is specified. This undermines clarity; the tool likely relies on context, which should be documented.

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 (opens), the resource (a Notion page), and the mechanism (deep link). It distinguishes from sibling tools like notion_read_page and notion_list_pages, making the purpose specific.

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 the tool is for opening a page in the desktop app but does not explicitly state when to use it versus alternatives (e.g., notion_read_page for content access). No exclusions or context provided beyond the one-line purpose.

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