upload_file_as_block

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It does not mention any side effects, safety considerations, file size limits, permissions, or whether the operation is reversible. The description only states what the tool does (upload and insert), but lacks crucial behavioral context for an AI agent to use it safely.

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, front-loaded with the primary action, and uses a clear structure: purpose statement, analogy to sibling, then parameter list. Every sentence adds value, and there is no redundant or unnecessary information.

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 zero schema coverage and no annotations, the description provides adequate information for basic usage: what the tool does, how parameters work, and differentiation from a sibling. However, it lacks details on file access requirements, error handling, or the nature of the output (though an output schema exists). It is mostly complete for typical use but could be more thorough.

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 schema has 0% description coverage, but the description compensates with an 'Args' section that explains all five parameters: file_path (local path), after_block_id (insertion position), parent_id (fallback location), caption (optional), and name (display override). These explanations add meaningful context beyond the schema's property names, though some are brief (e.g., 'Optional caption').

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 'Upload a file (PDF, doc, any attachment) to Notion and insert as a file block,' specifying the action and resource. It also distinguishes itself from the sibling tool 'upload_image_as_block' by noting it is for non-image files, which provides clear 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 explicitly states it is analogous to upload_image_as_block but for non-image files and recommends use for PDFs, spreadsheets, archives, etc. This gives clear context for when to use the tool relative to its sibling, though it does not explicitly state when not to use it or mention alternatives like the generic upload_file tool.

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