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

Beyond the annotations, the description discloses capacity limits, post-expiry read access, publication behavior, retention semantics, no-store responses, and the untrusted nature of uploaded text. These are useful behavioral and security details, though some statements are broad product policy rather than operation-specific permissions for reading an image.

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 purpose is front-loaded, but the description runs many sentences and includes peripheral policy details about purchases, uploads, replacement, and removal that do not directly help an agent invoke this read operation. Several sentences do not earn their place for this specific tool.

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 purpose, account context, and publication/security semantics, but it never explains the return format for an image download despite there being no output schema. It also omits clear access distinctions versus public/team image-reading siblings.

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 100%, so the schema already documents all three required parameters. The description does not add meaning beyond the schema for base_id, document_id, or image_sha, so the baseline of 3 applies.

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 first sentence states a specific verb and resource: "Download a verified image from the document." This clearly identifies the operation as image retrieval, though it does not explicitly distinguish it from sibling tools such as read_base_pdf_source or public_read_base_image.

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 account and policy context but no explicit guidance on when to use this tool versus alternatives like read_base_source, public_read_base_image, or team_read_base_image. It does not state when-not to use it or what prerequisite access distinguishes it from related read tools.

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