Insert an image

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

The description richly discloses behaviors beyond the annotations: URL validation constraints, local file upload and subsequent Drive deletion, native proportion handling, point-based positioning, and the returned objectId. This is especially valuable because the annotations are sparse (readOnlyHint=false, destructiveHint=false). No contradiction with annotations exists.

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 dense but front-loaded with the core purpose, followed by essential constraints and side effects. Every sentence and parenthetical carries needed operational information; nothing is filler.

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?

For a 9-parameter tool with no output schema and minimal annotations, the description is thorough: it covers input validation, cleanup behavior, sizing defaults, coordinate units, and the return value. An agent has enough context to invoke 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?

Although schema coverage is 100%, the description adds significant meaning by specifying validation limits (https-only, no private hosts, ≤2 kB URL; PNG/JPEG/GIF ≤50 MB, ≤25 megapixels), the disposable temp-file lifecycle, and how omitted size parameters behave. This goes well beyond the schema's basic field descriptions.

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 action ('Inserts an image on a slide') and identifies the underlying operation (batchUpdate createImage). It does not explicitly distinguish this from the sibling replace_image tool, so it lacks the full sibling-differentiation that would earn a 5.

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 explains the two mutually exclusive input modes (image_url or image_path) but gives no guidance about when to prefer this tool over alternatives such as replace_image or batch_update. There is no explicit when-to-use or when-not-to-use context.

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