Add Layout Picture

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

No annotations are provided, so the description carries the burden. It states that the tool adds a picture/SVG to a layout and mentions position/size in mm, but does not disclose error handling for missing files, overwriting behavior, or any side effects.

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 two sentences long with no waste. It front-loads the core purpose and adds essential parameter context efficiently.

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 no output schema, no annotations, and 6 parameters with 0% schema description, the description covers the core purpose and key parameter info (path, mm units) but lacks details about layout_name, file restrictions, and behavior. It is brief for a tool with this many parameters.

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 0% (no parameter descriptions in schema). The description adds that path is an image/SVG file path and that position/size are in mm, but does not explain layout_name (required) or clearly map each parameter (x, y, width, height) to their roles. This is partial compensation.

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 verb 'Add' and the resource 'picture or SVG (logo, north arrow) to a print layout'. This distinguishes it from sibling tools like add_layout_label or add_layout_map which serve different purposes.

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 provides context on when to use the tool (adding images or SVGs to layouts) and mentions that path is an image or SVG file path. However, it does not explicitly state when not to use it or provide alternatives, but the purpose is specific enough that it's clear.

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