upload_image_as_block

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation and reach profile is known. Beyond that, the description adds genuinely useful context: the image is stored in Notion's own workspace storage, so no external image host is required, which informs the agent about side effects and dependencies. Auth/permission requirements and overwrite behavior are still unstated, keeping it below 5.

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?

It is front-loaded with the one-sentence purpose, followed by a short storage note that earns its place, then a structured Args block. The closing constraint sentence is repeated logic already implied by the Args entries but is worth keeping for emphasis; otherwise there is little waste.

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?

An output schema exists, so return values need not be described, and the description covers insertion semantics, storage location, and parameter meanings for a mutating tool with four parameters. The remaining gap is operational: no mention of required permissions, size/format limits, or what happens on failure to upload.

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 carries the full burden, and it does document all four parameters: file_path with accepted image formats, after_block_id as the sibling insertion anchor, parent_id as the fallback append target, and caption as optional text. It also adds a cross-parameter constraint ('exactly one of after_block_id or parent_id') that the schema does not encode, which is real added value; it stops short of explaining the behavior when neither is supplied.

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 opens with a precise verb+resource+outcome: upload an image file to Notion and insert it as a new image block. It is distinguishable from generic file upload because it explicitly says 'image' and 'image block', though it never names upload_file_as_block or replace_image_block as the sibling alternatives, so the differentiation is inferential rather than stated.

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?

It gives a clear placement rule: use after_block_id to insert as a sibling, or parent_id to append to a page/block, and states the hard constraint that exactly one must be provided. What it lacks is guidance on when to choose this tool over upload_file_as_block or replace_image_block, so the routing guidance between siblings is absent.

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