insert_doc_image

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

No annotations are provided, so the description must carry the full burden of behavioral transparency. While it states the action, it does not disclose that this is a write operation requiring edit permissions, nor does it mention any side effects, error conditions, or reversibility. This is a significant gap for a mutation tool without annotation support.

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 concise and well-structured with an 'Args' section listing parameters and a 'Returns' section. Every line adds value, and there is no redundant or excessive text. The format makes it easy to scan and understand.

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?

All six parameters are clearly explained, and the return type is specified. The tool's complexity is moderate, and the description covers the essential aspects. However, it lacks details on prerequisites (e.g., user authentication, edit access) and error handling, which would be expected for a write operation without annotations.

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?

The schema has 0% description coverage, so the description is the sole source of parameter meaning. It explains each parameter in plain language: user email, document ID, image source (Drive file ID or public URL), zero-based index, and optional width/height in points. This fully compensates for the schema's lack of descriptions and adds meaningful context.

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 starts with a specific verb and resource: 'Inserts an image into a Google Doc from Drive or a URL.' This clearly distinguishes it from sibling tools like insert_doc_elements by focusing specifically on image insertion and the source locations. Even without mentioning siblings, the purpose is unambiguous.

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 makes the use case clear (inserting an image into a Google Doc) and explains the image source options. However, it does not explicitly differentiate this tool from the broader insert_doc_elements tool or state when not to use it. The usage context is implied, not directly contrasted with alternatives.

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