set_image_action

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

No annotations are provided, but the description mentions the return object format {image, kind, action_type, changed} and indicates it is analogous to set_textbox_action. However, it does not disclose side effects, permissions, or what 'changed' means, leaving some ambiguity.

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, front-loaded with the sibling comparison, and contains no redundant information. Every sentence adds value.

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 the tool has 5 parameters, no output schema, and no annotations, the description is incomplete. It fails to explain critical parameters like target_expression and drillthrough_parameters, and does not cover error situations or constraints, leaving agents guessing.

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?

The description adds almost no meaning beyond the schema; it does not explain the parameters (path, image_name, target_expression, drillthrough_parameters) or their roles, relying on the schema alone. The mention of 'same shape as set_textbox_action' is indirect, and schema coverage is 0%.

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 it operates on a named Image and sets an action type (Hyperlink/Drillthrough/BookmarkLink), distinguishing it from the sibling set_textbox_action which operates on textboxes.

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 images by saying 'operates on a named <Image>', but does not explicitly state when to use this tool versus alternatives like set_image_sizing or set_textbox_action, nor does it describe prerequisites or context.

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