upload_image_as_block

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

Discloses that the image is stored in Notion's own workspace storage, which is useful. However, without annotations, more transparency is expected regarding auth, rate limits, or error handling; does not fully compensate.

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?

Description is efficient with bullet points for parameters, no wasted sentences. Could be slightly more concise but well-structured and easy to parse.

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?

Covers main purpose and parameter usage well. Since output schema exists, lack of return value details is acceptable. Missing file size limits or supported formats beyond the list, but overall sufficient for an agent.

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?

With 0% schema description coverage, the description lists all 4 parameters with brief explanations and adds a constraint on the mutual exclusivity of after_block_id and parent_id, adding significant meaning beyond the schema.

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 uploads an image to Notion and inserts it as an image block, differentiating it from similar tools like upload_file or upload_file_as_block by specifying 'image' and mentioning it as a replacement for imgur-hosted images.

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 guidance on when to use (standard replacement for imgur-hosted images) and a critical rule: exactly one of after_block_id or parent_id must be provided. Lacks explicit when-not or alternatives to other siblings.

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