notion_page_summarize

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

The description only mentions routing through the domain-agent dispatcher under JWT/tenant/company scope. It does not disclose what side effects page_summarize may have, what content it acts on, or that the destructiveHint=true annotation implies possible modification or deletion. The description neither contradicts nor meaningfully enriches the 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 short, front-loaded with the action name, and contains no filler. The Args list is compact and readable, though the phrase 'Run the notion domain agent action' is somewhat redundant with the tool name.

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 domain-agent wrapper with a destructive hint and two free-form parameters, the description is under-specified. It does not explain what page_summarize is meant to do, what a valid objective looks like, what inputs are expected, or when an agent should choose this over sibling Notion tools.

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 only provides titles and defaults, so the description's 'message: Free-text objective' and 'inputs: Optional JSON string of structured inputs' add useful meaning. However, the descriptions are generic and give no indication of what JSON keys or message formats page_summarize actually accepts.

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 says only 'Run the notion domain agent action `page_summarize`', which essentially restates the tool name without explaining what summarizing a Notion page entails. It identifies the action but not its function, result, or distinction from the many sibling Notion tools like notion_query_data or notion_get_page_markdown.

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 when-to-use guidance, exclusions, or alternatives are provided. The only usage hint is that 'message' is a free-text objective, but there is no instruction on when to use this domain-agent wrapper versus the direct notion_* tools or the other notion_* domain actions.

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