add_image

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

With no annotations, the description carries the full behavioral burden and only partially meets it. It does disclose useful behavior (aspect-ratio preservation when w or h is omitted) but says nothing about whether the image is embedded or linked, what happens with an out-of-range index or unreachable URL, whether existing content is affected, or what the call returns.

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?

Front-loaded one-line summary followed by a compact Args block; every line adds meaning. The docstring formatting is slightly verbose for a tool description, but nothing is padded or redundant.

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 6-parameter mutation tool with zero annotations and no output schema, the argument semantics are complete but the operational context is not. An agent still cannot tell what the tool returns, whether the slide must pre-exist, or how errors surface.

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 description coverage is 0%, and the description fully compensates: index is zero-based, source is a path or http(s) URL, x/y/w/h are in inches, x/y are left/top, and w/h are optional with aspect-ratio coupling. Units and the mutual-exclusion rule are exactly the semantics the schema lacks.

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 first line gives a specific verb and resource ('Insert an image') plus the two accepted source types (local path or http(s) URL), which is enough to distinguish it from add_text_box and add_slide. It stops short of naming a sibling alternative or stating which presentation/slide context it operates on.

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?

There is no when-to-use or when-not-to-use guidance: nothing says the slide must already exist, how 'index' relates to list_slides, or whether open_presentation must be called first. The agent must infer the whole call sequence from the sibling list.

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