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

No annotations are provided, so the description carries the full behavioral burden. It does not state whether scanned/image PDFs are supported, whether large documents are chunked or truncated, whether a URL fetch requires network permissions, or what the returned Markdown looks like. It implies a conversion but discloses no operational traits.

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 purpose is front-loaded in a single sentence, followed by a compact Args block that documents each parameter with no filler. Every line carries information.

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 two-parameter converter with no output schema and no annotations, the description names the output type (Markdown) but not its return shape, and it omits the key routing context (scanned PDFs → ocr, tables → pdf_tablas) that would make it self-sufficient. Adequate but with clear holes.

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 compensate, and it does: 'fuente' is explained as either a public URL or base64-encoded content, and 'paginas' is given a concrete format example (`1-5,9`) plus the default behavior ('Sin valor, todas'). Only minor gaps remain (e.g., allowed URL schemes, base64 size limits).

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+resource: 'Convierte el PDF a Markdown'. The added detail 'con títulos y listas detectados por forma' implies a structural conversion that differs from sibling pdf_texto (plain text) and pdf_tablas (tables), though it never names those siblings explicitly.

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?

There is no guidance on when to choose this tool over pdf_texto, pdf_tablas, ocr, or docx_texto. The closest thing to context is the 'por forma' hint, which requires the agent to infer that scanned PDFs belong to ocr and tabular extraction to pdf_tablas.

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