extract_markdown_advanced

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

With no annotations, the description must carry the full burden. It discloses the return type and key parameters, but does not mention access permissions, rate limits, or side effects. Since extraction is inherently read-only, the description is adequate but not rich.

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 concise one-sentence summary followed by a structured argument list and return statement. No unnecessary text, and the structure is front-loaded and easy to scan.

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?

The description covers all parameters and the return value, which is sufficient for a tool of this complexity. It lacks guidance on choosing this over simpler alternatives, but is otherwise complete for an extraction task.

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%, and the description fully compensates by explaining each parameter: file_path (absolute path, PDF/image), pages (1-indexed), table_format_ (markdown/html), model (with default). This adds clear meaning beyond the raw schema types.

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 'Extract markdown with advanced OCR options', providing a specific verb and resource. The 'advanced' qualifier distinguishes it from the basic 'extract_markdown' sibling tool.

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 implies usage for scenarios requiring advanced OCR (model selection, pagination, table formats) but does not explicitly state when to use this tool over alternatives like 'extract_markdown' or 'extract_markdown_from_url'. No exclusions or alternative comparison is provided.

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