insert_picture

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

No annotations are provided, so the description carries the full burden. 'Insert' implies mutation, but the description does not disclose whether the picture is embedded, how the path is resolved, whether existing content is affected, or what happens after insertion. This is a minimal behavioral statement with significant gaps.

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 a single concise sentence with no filler and is easy to parse. It is front-loaded and grammatically direct, though its brevity borders on under-specification rather than efficient completeness.

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 the presence of an output schema, the tool has 6 parameters, no annotations, and zero parameter coverage in the description. It lacks essential context about required inputs, behavior, and how it differs from related insertion tools, so an agent would struggle to invoke it correctly.

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% across 6 parameters, and the description adds no meaning to any parameter. It does not explain required doc_id and image_path semantics, nor optional width, height, embedded, or size_option behavior. The description does nothing to compensate for the schema's lack of parameter documentation.

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 a specific verb ('Insert') and resource ('a picture into the document'). However, it does not distinguish this tool from the closely related sibling 'insert_background_picture', and 'insert_file' could also insert image content. This is clear but lacks sibling differentiation.

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 about when to use this tool versus alternatives, prerequisites such as having a document open, or whether this tool is appropriate only for inline images. The description only restates the basic action without any when-to-use context.

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