notion_update_page_markdown

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

With no annotations, the description must disclose behavioral traits, but it does not. It doesn't mention whether the tool mutates data, required permissions, or any side effects.

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 includes boilerplate routing information (URL, JWT, tenant, company scope) that is not helpful for understanding the tool's purpose. The core functionality is barely mentioned.

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 Notion update operation, the description is grossly incomplete. It does not explain how to construct the arguments, what the markdown content represents, or how this tool differs from other Notion update 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 single 'arguments' parameter has 0% schema description coverage. The description adds nothing beyond the schema: it just repeats 'JSON string of arguments' without specifying expected keys or valid values.

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 merely restates the tool name as 'Notion connector operation update_page_markdown' without specifying what the tool does. It fails to differentiate from sibling tools like notion_update_page or notion_replace_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 guidance is provided on when to use this tool instead of alternatives. The description only mentions routing details, which are irrelevant for usage decisions.

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