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

Annotations provide no hints (all false), so the description carries the full burden. It discloses timing (returns when detection finishes, usually under two minutes), billing (first 5 free), and retention behavior (ephemeral deletion after 60–70 minutes). This goes beyond the annotations and gives useful side-effect context. It does not contradict annotations.

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 a solid paragraph with every sentence adding value: conversion purpose, input options, timing, library hint, billing, and retention. It is not overly verbose, though the retention explanation could be tighter. Front-loads the core purpose.

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 details are not required. The description covers inputs, timing, billing, and retention, but leaves a critical ambiguity: it implies a PDF source is needed (pdf_url or pdf_base64) yet the schema marks both optional, and the title parameter is unmentioned. This could cause an agent to call it without a PDF. Completeness is adequate but has clear gaps.

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 description coverage is 0%, so the description must explain parameters. It does explain pdf_url (public https link), pdf_base64, library (slug from find_form), and retention (ephemeral or account_default), adding meaning beyond the schema types. However, it omits the title parameter entirely, so it does not fully compensate for the schema's lack of documentation.

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 clearly states the tool converts a flat or scanned PDF into a fillable PDF with detected fields, using a specific verb and resource. However, it does not explicitly distinguish this from sibling tools like prepare_form or fill_form, so it misses the differentiation criterion for a 5.

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 gives a clear context (turning a PDF fillable) and a usage hint about using library from find_form, but it never states when to use this tool versus alternatives or when not to use it. There is no explicit exclusion of other siblings, so guidance is implied rather than stated.

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