pdf_extract_text

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

The description adds value beyond annotations by explaining the default page limit and rationale. Annotations already indicate readOnlyHint=true and destructiveHint=false, so the tool is safe. The description further clarifies behavior (returns text, limited pages) without contradicting annotations.

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 extremely concise, consisting of two sentences. The first sentence states the core purpose, and the second provides essential details about defaults and parameter usage. There is no extraneous information; every sentence serves a purpose.

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 the tool's simplicity and the presence of full schema coverage and annotations, the description is complete. It covers purpose, default behavior, and parameter usage. It does not specify the output format (e.g., plain text), but that is implicitly clear. For a non-complex tool, this is sufficient.

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 the parameters are well-documented in the schema. The description reinforces the purpose but does not add new semantic meaning. It mentions the default for 'pages' which is also in the schema. Score is baseline due to high schema coverage.

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 the action 'Extract text content from a PDF file', which is a specific verb and resource. It distinguishes from sibling tools like pdf_add_page_numbers or pdf_merge, which have different purposes. The default behavior of returning first 10 pages is also noted, adding clarity.

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 explains when to use the default (first 10 pages) and how to use the 'pages' parameter for more control. It provides context about avoiding LLM context limits, but does not explicitly mention when not to use this tool or suggest alternatives. Overall, it gives clear usage guidance.

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