notion_upload_file_to_database

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

With no annotations, the description is the sole source of behavioral context. It adds useful details about accepted source schemes, case-sensitivity of the files_property, and the need to verify column names with notion_describe_database. However, it does not disclose failure modes, idempotency, permissions, or side effects beyond creating a row, leaving some gaps.

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 starts with a clear one-sentence purpose and then lists parameters in a structured, scannable format. It is concise (about 120 words) with no filler, and each line adds essential information. The only minor issue is that it could be slightly tighter in wording, but it remains effective.

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?

For a six-parameter create-operation tool, the description covers the main workflow, required inputs, and source scheme details, and it references the cross-MCP handoff pattern. It does not discuss return values or edge cases, but an output schema exists to cover return format. The description is sufficiently complete for accurate invocation.

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 description provides rich semantic detail for most parameters: source scheme syntax, files_property case-sensitivity and verification, title behavior, and override purposes. This goes well beyond the bare schema and compensates for the 0% schema description coverage. Even database_id is self-evident from the tool name.

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's function: uploading a file and creating a new row in a Notion database with the file attached to a specified files & media column. It uses a specific verb ('upload') and resource ('database row'), and explicitly says 'NEW row' to distinguish from tools like notion_add_file_to_row that add files to existing rows.

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 implies the tool is for creating a new row with a file attachment, while siblings like notion_add_file_to_row serve existing rows. It references notion_upload_file for source scheme details, which guides the user on prerequisite knowledge, but it does not explicitly say when not to use this tool or name alternatives. The purpose is clear enough for the agent to select correctly in most cases.

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