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

With no annotations present, the description carries the full transparency burden. It openly discloses async behavior ('Returns a job_id; waits up to wait_seconds for completion'), the 20 MB file limit, the quota consumption, and the input_key requirement. It does not describe failure modes or error responses, but it covers the key operational traits an agent needs to call the tool correctly.

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 every sentence earns its place: formats, upload procedure, size limit, behavioral warning, return behavior, and quota. The purpose is front-loaded and the critical instructions are placed early. The curl example adds length but is essential operational detail rather than filler.

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 tool with five parameters, nested options, no annotations, and no output schema, the description covers the full workflow: upload, conversion, wait behavior, and resource consumption. It could mention how to retrieve results via siblings like brode_download or brode_job_status, but those sibling tools are visible and the job_id handoff strongly implies the next step.

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 coverage is 80%, so the baseline is 3, but the description adds real value beyond the schema. It clarifies that input_key must come from the specific upload endpoint, groups output formats into vector vs embroidery categories, and explains wait_seconds behavior in the conversion flow. This helps an agent reason about how the parameters fit together.

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 resource: 'Convert a raster image ... to a vector format ... or a machine embroidery file.' It explicitly lists acceptable input and output formats, making the tool's scope unambiguous. It also clearly distinguishes itself from siblings like brode_download, brode_job_status, and brode_presets by describing a conversion-specific responsibility.

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 strong practical guidance: upload the file once via the provided curl command, pass the returned input_key, and wait for completion. It also warns not to read, compress, or base64 the image. It does not explicitly name alternative tools for download or status checking, but the workflow context and sibling names make the intended usage clear.

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