add_image_base64

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

No annotations are available, so the description must reveal behavioral traits. It indicates the tool modifies the document ('Add an image'), but does not disclose constraints like potential destructive actions, required permissions, or behavior with invalid data. Minimal transparency.

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?

Extremely concise with a clear front-loaded purpose, followed by parameter descriptions and return value. Every sentence serves a purpose with no wasted words.

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?

The tool has few parameters and an output schema (implied), so the description covers basic usage. However, it lacks important behavioral context (e.g., supported image types, error handling) and usage differentiation from siblings. It is minimally complete but not robust.

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 add value. It explains that base64_data can include a data URI prefix and that width_inches is optional. While not exhaustive, these clarifications go beyond the schema titles. However, it does not describe the accepted image formats or size limits.

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?

Description clearly states 'Add an image from base64 encoded data' with specific verb and resource. However, it does not distinguish from sibling tools like 'add_image' or 'save_base64_as_image', which may cause confusion about which tool to use.

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 provided on when to use this tool versus alternatives. Lacks context about prerequisites (e.g., document must be open), supported image formats, or size limits. The description does not mention when not to use it.

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