Get an Excel conversion

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

Annotations only declare openWorldHint, so the description carries the rest and does add real value: it discloses that the call blocks until the conversion finishes, that the download link is regenerated on every call (so an old link can't be reused), and that it's free. It does not say what is returned while the job is still running or on failure.

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?

One short sentence pair with the three key facts front-loaded (action, blocking wait, local save) followed by the caching and cost notes. Nothing is padding.

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 the description does hint at a download link in the response, but it doesn't say whether the call returns a status object, where the link appears, or what happens if the conversion failed. For a two-parameter polling tool, this is nearly complete but leaves the return shape under-specified.

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 50%; save_to is already fully documented in the schema and the description's 'optionally save the .xlsx locally' mostly restates it. The required, undocumented conversion_id is never explained — notably that it comes from convert_to_excel — so the gap is not compensated.

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 concrete verb and resource: check an Excel conversion, wait for completion, optionally save the .xlsx. It implicitly contrasts with convert_to_excel (which creates the job) but never names a sibling, so the differentiation is left to inference.

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 phrase 'wait for it to finish' implies this is called after convert_to_excel to poll/await a result, but the description never says so or explains when to use this instead of get_job or wait_for_jobs, which overlap heavily.

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