preview_notion_publication

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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description reinforces the safety profile by promising no Notion writes and adds the meaningful precondition that the draft must be approved and the task selection explicit. It does not discuss failure modes (e.g., what happens with an unapproved draft or empty selection), which is a minor gap since an output schema covers return shape.

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?

Two short sentences, zero padding, with the core action and the no-write guarantee both front-loaded. Every clause earns its place.

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?

With an output schema present, the description needn't explain return values, and it does cover what is previewed and the write-safety guarantee. The remaining gap is the ambiguous meaning of the index array and version semantics, which neither schema nor description resolves.

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 coverage is 0%, so the description must carry the burden. It maps reasonably onto the three params — 'one approved draft version' implies draftId and version, and 'explicitly selected Tasks' implies selectedNextActionIndexes — but it never clarifies that the indexes are 0-based positions into the draft's next actions, nor how version interacts with draftId.

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?

States a specific verb (Preview) plus the exact resources (Work Logs and explicitly selected Tasks) and scope (one approved draft version). The Notion framing plus the sibling names publish_to_notion and preview_calendar_publication make it easy to place this tool without opening a schema.

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 phrase 'for one approved draft version' establishes the precondition that a draft must already be approved, and 'This performs no Notion writes' signals this is the safe inspection step before publishing. It stops short of explicitly naming publish_to_notion as the follow-up action or excluding cases where preview is unnecessary.

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