pdf_corpus_overview

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

The description discloses security concerns (untrusted data) and caching/warming behavior (time budget, unprocessed docs), which are key behavioral traits. No annotations were provided, so the description carries full responsibility.

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 includes a necessary but lengthy security warning, yet the core functionality is stated concisely. It is front-loaded with important context.

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?

Given high schema coverage and presence of an output schema, the description covers essential behavior. However, it omits the file cap (100 files) mentioned in the schema, which is a minor gap.

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 baseline is 3. The description repeats the idea of 'folder or list' and 'time budget' but does not add significant extra meaning beyond the schema.

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 specifies a clear verb ('Get') and resource ('per-document triage card') with scope ('every PDF in a folder or list'), and the tool is easily distinguished from siblings like pdf_render_pages and pdf_extract_chart.

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 provides context on when to call again ('unready docs appear in unprocessed; call again to continue'), but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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