add_header_image

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

With no annotations, the description must fully disclose behavior. It explains image_source options but does not mention side effects, permissions required, or whether it overwrites existing images. The description is minimal beyond parameter hints.

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 one sentence with relevant info, no filler. It could be slightly more structured but is efficient.

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?

The tool has 8 required parameters and no output schema, but the description only covers image_source and value. It omits important details like measurement units for top/left/width/height and naming conventions for path and name. The description is incomplete for proper 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 description coverage is only 13% (only 'value' described). The description adds meaning to image_source and value (explaining the three sources), but does not explain top, left, width, height, name, or path. It partially compensates but not sufficiently for low coverage.

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 adds an image to PageHeader/ReportItems, uses specific verb-add and resource-header image, and differentiates from siblings like add_body_image and add_footer_image by specifying the header context.

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 for adding images to headers but does not explicitly state when to use this tool over alternatives like add_body_image or add_footer_image, nor does it mention any prerequisites or exclusions.

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