Publish Notion document

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

Annotations already indicate destructive and non-read-only behavior. The description adds valuable context about conflict-safe edits, bounded rebasing, and post-write verification, which goes beyond the annotations and helps the agent understand the tool's 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 is a single, dense sentence that packs in the core functionality and key behaviors. Every word adds value, with no wasted fluff.

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's high complexity (multiple modes, conflict policies, operations), the description covers the main scenarios and safety features. It relies on the schema for detailed parameter structure, which is appropriate since no output schema exists.

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?

Schema description coverage is 56%, and the description doesn't detail parameter meanings. It provides a high-level overview but relies on the schema for specifics. Since coverage is moderate, the description adds some context but doesn't fully compensate for undocumented parameters.

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 tool creates one or more Notion documents or applies edits to a document. It specifies the write nature and distinguishes itself from the sibling notion_read_document by focusing on creation and editing rather than reading.

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 usage for writing/creating Notion documents, making it clear when to use this tool over the read-only sibling. However, it doesn't explicitly mention when not to use it or provide alternative tool references, so it falls short of a 5.

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