notion_list_file_uploads

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the status filter values and the limit range, but omits pagination/ordering behavior, permission requirements, and how results are sorted or truncated. Adequate but with meaningful gaps for a list 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?

Three short lines with zero waste: purpose first, then each parameter explained in one clause. Nothing is repeated or padded.

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?

With an output schema present, return values need not be explained, and both parameters are covered. However, with no annotations and no schema parameter descriptions, the description should say more about operational behavior (pagination, permissions, result ordering). It is complete enough to call but not fully self-sufficient.

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 0%, so the description must compensate for both parameters. It does so well: it enumerates the status values (pending | uploaded | expired | failed) and states the limit range (1-100), which the schema lacks. It omits the default values (limit 20, status empty), leaving a small gap.

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?

States a specific verb and resource ('List files this integration has uploaded to Notion') with a clear scope limited to the integration's own uploads. This distinguishes it from siblings like notion_list_files_on_page and notion_list_local_files, though it does not name those alternatives explicitly.

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?

Provides clear usage context ('useful for checking an import or finding an upload ID'), telling the agent when this tool is appropriate. It does not state exclusions or point to alternatives, which keeps it below a 5.

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