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

Annotations already mark this as a read-only, open-world operation, so the safety profile is covered. The description adds one valuable behavioral fact — a completed job yields an absolute, temporary download URL — but does not disclose job states (pending/failed), whether URLs expire after a fixed period, or error behavior.

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?

Two tight sentences with the core purpose front-loaded followed by the key output fact. No 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?

An output schema exists, so return values need not be explained, and annotations cover the read-only nature. However, the description omits where job_id originates and any polling guidance, which are meaningful gaps for a status-check tool.

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 single parameter job_id has 0% schema description coverage, and the description does not explain where the job ID comes from (presumably returned by a conversion call) or its format. That leaves the only required input under-specified in both places.

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 ('check') and resource ('DOCX.now conversion job'), which clearly separates it from the sibling converters like list_converters and convert_image_url. It does not explicitly name alternatives, but the resource noun alone is enough to tell an agent what the tool targets.

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?

Usage is implied — you check a conversion job after starting one — but the description never says so, nor does it mention polling cadence or when to prefer another sibling. There are no explicit when-not conditions.

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