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

The description goes well beyond the sparse annotations (readOnlyHint=false, destructiveHint=false). It discloses engine auto-picking from the conversion graph, magic-byte detection behavior, and the critical gotcha that text-based inputs require 'from' because they lack magic bytes. It also states the business-tier requirement.

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 a clear purpose and example, and the magic-byte warning is valuable. However, 'Business tier only' and '[requires the business plan]' are redundant, and the 'category: convert' tag adds marginal value, so it is slightly less tight than it could be.

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 3-parameter tool with full schema coverage, the description covers the essential semantics: step count, engine selection, input format detection, text-input warning, file size limit, and tier restriction. It does not describe return values or enumerate supported formats, but that is a minor gap given the richness of the schema and description.

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 100%, so the baseline is 3. The description adds meaning by explaining that each step's engine is auto-picked from the conversion graph, which clarifies the optional 'engine' field in the steps schema. It also reinforces the 'from' parameter's practical necessity for text-based inputs.

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 uses a specific verb and resource: 'Run a 1-5 step conversion pipeline in one job,' with a concrete example (docx → pdf → epub). This clearly distinguishes it from single-step converters like convert_file or convert_document among the siblings.

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 clearly indicates this is for multi-step conversion jobs ('1-5 step conversion pipeline in one job') and includes the business-tier restriction. However, it does not explicitly name alternatives or state 'use convert_file for a single conversion step,' so the when-not-to-use guidance is implied rather than explicit.

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