docs_insert_image

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It lacks any mention of where the image is inserted (e.g., at an index or at the end), whether the URL must be publicly accessible, what happens if the URL is invalid, or how the width_pt and height_pt parameters affect the image. This is a significant gap for a mutation tool.

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 one-sentence description is highly concise and front-loaded, containing no filler or redundant information. It states the essential action and resource in a clear, efficient manner, which is appropriate for the tool's apparent simplicity.

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 having an output schema and several parameters, the description provides no context about insertion behavior, constraints, or error handling. The presence of index, width_pt, and height_pt implies additional functionality that is completely unaddressed. The description is too bare to fully enable correct tool usage without external knowledge.

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, and the description itself adds no parameter information beyond what the schema names imply. The optional parameters index, width_pt, and height_pt are not explained, leaving the agent to guess their meaning and behavior. Since the description must compensate for the low schema coverage and fails to do so, the score is minimal.

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 tool's function: inserting an image into a Google Doc from a URL. The verb 'insert', the resource 'Google Doc', and the source 'URL' are specific and distinct from sibling tools like docs_insert_text or docs_insert_table. There is no ambiguity about what this tool does.

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 implies usage when the user wants to add an image from a URL to a Google Doc. However, it provides no explicit guidance on when not to use this tool or alternatives, such as using slides_insert_image for slides or docs_insert_text for textual content. The context is evident from the name but not explicitly stated.

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