create_page_from_file

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

With no annotations, the description carries full burden. It thoroughly explains server behavior: reads and validates file, converts markdown to native Notion blocks (not flat text), automatically handles Notion's limits (100-block batching, 2000-char splitting, deep nesting), and returns a receipt with id, title, url, and note only at workspace root. It also notes what is not included (no block count, per-block IDs). No contradictions.

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 well-structured: first paragraph states core purpose and key behavior, second paragraph addresses mode restriction, third lists restrictions clearly, and fourth provides additional return value info. Every sentence adds value, no redundancy, and it is appropriately sized for the tool's complexity.

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 complexity (file validation, markdown conversion, Notion limits, return receipt), the description covers all necessary aspects. Although there is no output schema, the description explicitly states the return fields. It also references a resource for supported markdown syntax. It is sufficiently complete for an agent to use correctly.

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 100% already, but the description adds significant value: for file_path it elaborates on absolute path requirement, workspace root, extension, size, and UTF-8 constraints; for parent_page_id it notes 'same resolution rules as create_page' which aids understanding. This goes beyond the schema's minimal descriptions.

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 explicitly states 'Create a Notion page from a local markdown file' and distinguishes from sibling create_page by noting the same result but without sending file contents through agent context. This provides a clear, specific verb+resource with differentiation.

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 clearly states 'STDIO MODE ONLY' and explains why it's unavailable over HTTP, and enumerates restrictions (absolute path, workspace root, file extension, size, UTF-8, symlinks). However, it does not explicitly contrast when to use this tool vs create_page for scenarios where streaming file contents might be acceptable, but the comparison is implied.

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