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

With no annotations, the description carries the full behavioral burden and does so well: it discloses unlock-credit consumption for machine files, re-download behavior, free companion files, required Authorization header, and that responses are URLs rather than base64 payloads.

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 key purpose is front-loaded, followed by file-variant details, cost implications, and fetch instructions. Despite being dense, every sentence adds operational value for correct invocation.

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 lack of annotations and output schema, the description covers everything an agent needs: what is returned, how to fetch it, authentication requirements, and cost side effects. No critical gap remains for correct tool use.

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 the description adds meaningful semantics for each value, including default behavior and which variants exist for which job types. It also implies job_id refers to a completed conversion, though it does not further explain the UUID requirement 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?

States a specific verb and resource: downloading a completed conversion's result file or its companions. The enumerated file variants make the scope clear, but it does not explicitly differentiate itself from siblings like brode_convert or brode_job_status.

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?

Gives clear context that the conversion must be completed and advises checking the free preview before spending an unlock credit. It does not name alternative tools for related tasks, but the when-to-use guidance and cost caveat are strong.

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