Insert Doc Image

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

The description repeats the basic functionality but adds no behavioral detail beyond what annotations already convey (e.g., readOnlyHint=false, destructiveHint=false). It fails to disclose side effects, authorization needs, or constraints like image format or access restrictions.

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 wasted words. While it could include more structure or additional context, it is not overly verbose and communicates the core purpose efficiently.

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?

Given the presence of an output schema and full coverage of parameters, the description is minimally adequate. However, it could be more complete by mentioning whether the image is embedded or linked, or any size limitations, which would help the agent use the tool 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?

With 100% schema coverage, the parameter descriptions in the schema are already sufficient. The tool description does not add additional meaning or context to the parameters, so a baseline score of 3 is appropriate.

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 action (inserts), the target resource (image into a Google Doc), and the source (from Drive or a URL), making it unambiguous and distinguishing it from related tools like insert_doc_elements.

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?

The description does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites, caveats, or when not to use it. It is clear but lacks decision-support context.

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