upload_to_notion

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions only the high-level action, without addressing side effects (e.g., whether it creates a block or updates a property), permission requirements, error behavior, or the implications of different `attach_as` values. This is a minimal disclosure for a mutation-like operation.

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, clear sentence that efficiently conveys the core purpose without redundancy. It is front-loaded with the action and avoids filler, making it easily scannable.

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 (5 parameters, multiple attachment modes including image/file/cover/icon, and an optional property binding) and the lack of an output schema, the description is too sparse. It does not explain the different attachment modes, why one might choose a property versus a block, or how it relates to the sibling tool. The schema covers parameters, but the description should provide broader contextual guidance.

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 input schema has 100% description coverage, so the schema itself documents parameter meanings and constraints. The description adds little beyond the schema—it does not clarify the relationship between `page_id_or_url`, `property`, or `attach_as` choices, but that is adequately covered by structured fields.

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 action ('Upload a local file to Notion') and target ('attach it to a page'), using a specific verb and resource. However, it does not distinguish this tool from its sibling `upload_to_notion_at`, which likely offers a related but different attachment behavior.

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 provides no guidance on when to use this tool rather than the sibling `upload_to_notion_at`, nor does it mention prerequisites, exclusions, or typical use cases. It is purely a statement of function without contextual direction.

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