notion_send_file_upload

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

Annotations already carry the destructive/mutating and idempotent hints, so the description only needs to add context. It adds useful behavioral context with "effect: Claimed read or write effect; Spring verifies it" and "approval_ref: Approved platform task UUID when resuming a write", implying write operations need an approved platform task. No contradiction with annotations, but it does not explain the actual side effects of sending a file upload.

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 compact: one identification line, one routing constraint, and a seven-item argument list. Each bullet earns its place and the argument semantics are front-loaded after the operation identification. There is no padding or repetition.

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?

Despite having an output schema, the description is incomplete for safe invocation: it never defines the core behavior, what payload belongs in "arguments", how to obtain a valid approval_ref, or how this relates to the sibling file-upload operations. An agent cannot determine the correct call shape from this description alone.

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%, and the description compensates by giving every parameter a meaningful one-line gloss: project_id as Authenticated Project UUID, project_ref as exact correlation reference, idempotency_key as stable business-action identity, and effect as claimed read/write verified by Spring. The weakest is "arguments" (JSON string of arguments), which is vague about the actual payload shape, but the wrapper fields are clarified beyond the schema's bare titles.

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 identifies the tool as "Notion connector operation send_file_upload" but never states what the operation accomplishes—it only adds a routing constraint ("Routes only through the exact project/account governed connector authority"). This is close to restating the tool's name and does not distinguish it from sibling tools like notion_create_file_upload, notion_complete_file_upload, or notion_get_file_upload.

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?

No guidance is given on when to use this tool versus alternatives or what preconditions are required. The routing sentence is a constraint on how the call must be scoped, not a usage condition or exclusion. The agent is left to infer when send_file_upload is the right operation among the many Notion file-upload siblings.

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