upload_file

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

No annotations are provided, so the description must fully disclose behavior. It mentions the return value (file_upload_id), supported file types, and a size constraint (20 MiB single-part mode), but does not discuss permissions, error handling, or whether the operation is destructive.

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 concise and front-loaded with the core purpose. It includes a note about the return value, an alternative tool, and parameter details without excessive verbosity.

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 single parameter, existence of an output schema, and no annotations, the description covers the primary aspects: what it does, the return value, when to use an alternative, and the parameter's file type/size constraints. It could mention error scenarios or output schema details but is sufficient for a simple upload tool.

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 no description for file_path (0% coverage), but the description adds meaningful context: local path, supported file types (PNG, JPEG, GIF, SVG, PDF, etc.), and a size limit for single-part mode. This compensates well for the schema's lack of description.

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 uploads a file to Notion's own storage and distinguishes it from the sibling tool upload_image_as_block by noting the alternative for the common case of uploading an image and creating a block in one step.

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?

Explicitly advises using upload_image_as_block for the common case of image upload and block creation, providing a clear when-not scenario. However, it does not mention when to use upload_file_as_block instead.

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