pdf

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

Discloses cost per call, wallet requirement, output structure, and a size limit (up to 20MB). With no annotations, this provides essential behavioral context, though error handling and redirect behavior are omitted.

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?

Two concise sentences; first sentence front-loads the core action ('Fetch a PDF and extract text') without extraneous words. Every sentence provides value.

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 single-parameter tool with no output schema, the description covers core behavior, output, and limits. Minor gaps like error handling exist, but it is adequate for basic use.

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 contains full description of the 'url' parameter and coverage is 100%. The main description adds no extra detail about the parameter beyond the schema, meeting the baseline.

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 it fetches a PDF and extracts text, with specific outputs (page count, document info, full text). It distinguishes from siblings like 'screenshot' or 'extract' by focusing exclusively on PDFs.

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?

No explicit guidance on when to use this tool vs alternatives like 'extract' or 'screenshot'. The cost note implies a constraint but doesn't help the agent decide between sibling tools.

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