replace_image_block

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

Details the deletion-insertion behavior to preserve position, the edge case for first child, and a Notion limitation. Could also mention error handling but overall good transparency with no annotations.

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?

Efficient and well-structured: brief purpose, behavior explanation, then args list. No wasted sentences.

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 key aspects: purpose, behavior, parameters. Could mention return value or error states, but output schema exists to cover return.

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?

Explains all three parameters meaningfully: block_id as existing block, file_path as new image, and caption as optional with behavior for omission. Compensates fully for 0% schema coverage.

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?

Clearly states it replaces an existing image block's content with a newly uploaded image, and mentions preserving position, distinguishing from sibling tools like delete_block or upload_image_as_block.

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?

Describes behavior and a limitation (no prepend-at-position), but does not explicitly state when to use versus alternatives, nor when not to use.

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