insert_excel_image

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

No annotations are provided, so the description carries full burden. It mentions the action (insert) and output (confirmation with position and size), but does not disclose side effects (e.g., file modification, overwrite behavior) or requirements (e.g., file must not be open).

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 well-structured with a one-sentence summary and clear @param/@return blocks. It is appropriately sized for the tool's complexity, though it could be slightly more concise.

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 description covers all parameters, return value, and anchor behavior. Given that an output schema exists, return details are sufficient. It could mention edge cases or limitations (e.g., image size limits), but overall it is complete enough for effective use.

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 provides full parameter documentation (@param tags) with format examples and defaults, compensating completely for the 0% schema description coverage. It adds meaning beyond the schema for all 6 parameters.

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 inserts an image from a local file into a workbook, anchored at a cell. It uses a specific verb ('Insert') and resource ('image'), and distinguishes from sibling tools like extract_images or read_excel_data.

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 (inserting images) but does not explicitly state when to use this tool versus alternatives or provide exclusions. No guidance on prerequisites or conditions is given.

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