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

With no annotations provided, the description carries the behavior disclosure burden. It explains that the tool returns an absolute URL rather than the file itself, requires an 'Authorization: Bearer' header when fetching, returns filename/MIME/size, and never returns base64 due to tool-result budget limits. It does not discuss error cases, but the key operational behavior is well covered.

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 dense but front-loaded: it states the object, lists variants with formats, explains the return type and auth requirement, and closes with the base64 limitation. Every clause earns its place and there is no filler or redundant restatement of the tool name.

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?

There is no output schema and no annotations, but the description fully explains what the agent receives (absolute URL, filename, MIME type, size), how to access the file (Authorization header, curl example), and which file types are available under which conditions. An agent can correctly invoke this tool from the description alone.

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 schema documents the 'file' enum and default, but the description adds concrete meaning: preview is a PNG rendering, worksheet is an embroidery thread color chart PDF, and stitches is a stitch trace JSON. It also frames job_id as identifying the completed conversion whose file is being downloaded, which is adequate despite the schema not describing job_id beyond its type.

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 opens with a specific verb and object: 'Download a completed conversion's file', then enumerates exactly which artifacts are available (output, preview, worksheet, stitches). This clearly distinguishes it from siblings like brode_convert, brode_job_status, and brode_presets by action and resource.

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?

Scoping is clear: the tool is for completed conversions, and availability constraints are stated explicitly (preview/worksheet/stitches only exist for completed jobs; worksheet/stitches only for embroidery formats). It does not explicitly name sibling alternatives or give a 'when not to use' clause, but the context is clear enough.

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