download_doc_image

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

Without annotations, the description carries the burden of behavioral disclosure. It reveals a size constraint (payloads > 2 MiB require save_path) and implies the image is returned for the model to see, but does not specify the output format, authentication requirements, or 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 concise, with three sentences that front-load the core purpose and then add key usage details. It avoids unnecessary fluff, though the 'UAT-first' part is unclear and could be removed.

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 3 parameters, no output schema, and no annotations. The description does not specify the return value (e.g., binary data, file path) or error conditions. While it explains the size cap, it could be more complete regarding what the agent can expect after 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?

The input schema has 100% coverage, meaning each parameter has a description. The description adds value by explaining the origin of image_token (from get_doc_blocks), the purpose of doc_token (permission scoping), and the condition for save_path (payload > 2 MiB). This goes beyond the schema's own descriptions.

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 downloads an image embedded in a docx document, with a specific verb ('download') and resource ('image from docx'). It distinguishes itself from siblings like 'download_message_resource' by specifying the source (docx) and the context (get_doc_blocks).

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 explicit instructions on how to use the tool: pass the image_token from get_doc_blocks and optionally the doc/wiki/URL token for permission scoping. It also mentions a size cap and required save_path. However, it does not explicitly state when not to use this tool or compare with alternatives.

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