insert_doc_image

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

No annotations provided, so description carries burden. It discloses auto-conversion of Drive IDs, index 0 bump to 1, and OAuth scope requirements. Lacks error handling details but is otherwise transparent.

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?

Concise and front-loaded with main action. Each sentence adds value without redundancy. No fluff or unnecessary details.

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 output schema exists, return values need not be explained. All 6 parameters covered, behavior well-described, prerequisites and scope noted. Complete for correct tool invocation.

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 coverage is 100%, baseline 3. Description adds value by explaining image_source types and auto-conversion, index bump, and width/height default meaning (0=auto-size). Enhances schema understanding.

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 'Insert an image into a Google Doc from Drive or an HTTPS URL,' specifying the verb, resource, and data sources. It distinguishes itself from sibling tools like insert_slides_image (for Slides) and insert_doc_elements (more general).

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?

Provides explicit when-to-use and prerequisites: Drive files must allow 'Anyone with the link' and suggest checking with check_drive_file_public_access; HTTPS URLs must be direct image bytes. Also mentions supported formats and index behavior.

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