Parse a local file or document URL

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower, and the description adds genuine context beyond them: local-only parsing with no upload or conversion service, plus per-format conversion behavior (spreadsheets to tables, presentations to one section per slide, PDF hyphenation/column repair). It does not discuss cost, size limits, or failure modes on remote fetches, but the added context is substantive.

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 sentences, front-loaded with what the tool does, then supported formats, then conversion specifics, then the privacy guarantee. Each sentence carries distinct information and nothing is repeated from the schema.

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?

With no output schema, the description usefully explains the return shape (text as Markdown, with format-specific structuring), and the schema handles offsets and mutual exclusivity. What is missing is any guidance on large documents or when a remote URL fetch would fail, but nothing an agent needs to invoke it correctly is absent.

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 100%, so all five parameters — including the url/path mutual exclusivity, sheet selection, format enum, and max_chars truncation with next offset — are already fully documented in the schema. The description adds only the format list and conversion outcomes, not parameter-level meaning, so the baseline 3 applies.

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 (read/parse) and resource (document from a local path or URL) and names the exact output (text as Markdown), plus an enumerated list of supported formats. It never names a sibling such as fetch_url or web_search, so the agent must infer the boundary between 'parse a document' and 'fetch a URL' on its own.

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 its niche — documents (PDF, DOCX, XLSX, etc.) rather than arbitrary web pages — but gives no explicit when-to-use or when-not-to-use statement and no alternative tool named. The presence of fetch_url/fetch_urls among siblings makes that omission a real gap.

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