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

Annotations already declare read-only, idempotent, non-destructive, non-open-world behavior. Beyond that, the description adds important behavioral details: the 1 MB maximum, base64 encoding, and special image handling for PNG, JPEG, GIF, and WebP.

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 front-loaded with the core action and size limit, then gives alternatives and a reference URL. Every sentence adds useful routing or behavioral context without unnecessary repetition.

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?

For a read-only file retrieval tool with no output schema, the description explains the return representation, size cap, and image handling well. The main remaining gap is finer-grained parameter semantics for `path` and `briq`.

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 0%, so the description must carry parameter meaning. It implies that `briq` identifies the target filesystem and that `path` is a file path, but it does not explicitly document path format, relative vs. absolute resolution, or the `bq_...` identifier format beyond what the schema pattern shows.

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 states a specific verb and resource: downloading a file from the briq's own filesystem, with a clear 1 MB limit and base64/image return behavior. It distinguishes the tool from briq_exec by explaining that briq_exec is for text bytes or partial reads of larger files.

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?

It explicitly says when to use this tool, including that supported image types come back as viewable images. It also names alternatives for related cases: briq_exec with base64 for text bytes and head/tail/grep for files larger than 1 MB.

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