Convertir un PDF local a Markdown

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

No annotations provided; description notes 'sin gastar tokens en el binario' and 'No requiere sesión de Moodle,' which are helpful. It does not disclose error handling, file size limits, or whether the PDF is left unmodified. Score 3 as it adds some but not full context.

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?

Three concise sentences cover the core function, optional output, and authentication context. Every sentence adds value; no fluff. Could be slightly more structured, but effective.

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 simple conversion tool with no output schema, the description covers the main purpose, input, optional output, and token-saving benefit. It lacks details on return format but maxChars parameter partly addresses output control. Overall adequate.

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% with descriptions. The description adds that outPath optionally saves the result, but this is already in the schema. No additional semantics beyond the schema are provided.

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?

Description clearly states it converts a local PDF to Markdown/text, distinguishing it from sibling tools that deal with grades, courses, files, etc. The verb 'convertir' and the resource 'PDF a Markdown' are specific.

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 mentions 'No requiere sesión de Moodle,' which clarifies when to use (no session needed). It implies use when you have a local PDF and want to save tokens. However, it does not explicitly state when not to use or provide alternatives.

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