Add Picture

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

Annotations provide only a title with no behavioral hints (e.g., readOnlyHint). The description states it adds an image (a write operation) but does not disclose other behaviors like required file formats, insertion position, or error handling. With sparse annotations, the description should provide more behavioral context.

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 a single sentence, which is concise but lacks additional structure or details. It is not overly verbose, but it also does not earn its place by providing necessary context beyond the bare minimum.

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 3 parameters with no documentation, no output schema, and no behavioral hints from annotations, the description is severely incomplete. It does not explain return values, prerequisites, or implications of the parameters, leaving the agent with insufficient information to use the tool correctly.

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 input schema has 3 parameters with no descriptions (schema description coverage 0%). The tool description does not explain any parameter semantics, such as what 'filename', 'image_path', or 'width' mean. The description fails to add meaning beyond the schema.

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 specifies the action ('Add') and the resource ('image') and target ('Word document'). It distinguishes itself from sibling tools like add_heading or add_table by focusing on images.

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 does not provide explicit guidance on when to use this tool versus alternatives such as other 'add_*' tools. Usage is implied by the tool's specific function, but no exclusions or context are given.

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