Paper Pilot

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions downloading and returning a preview but lacks details on permissions, rate limits, error handling, or what 'local preview' entails (e.g., format, content). This leaves significant gaps for a tool that involves external resource access.

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 single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't explain the return value ('local preview'), error conditions, or dependencies, which are critical for a tool that downloads and processes external PDFs. The minimal information provided is insufficient for safe and effective 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 description coverage is 0%, so the description must compensate but fails to do so. It doesn't explain what 'pdf_url' should contain (e.g., format, validation) or the purpose of 'filename_hint' beyond its default. No parameter details are provided, leaving both parameters semantically unclear.

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 ('Download an open-access PDF') and outcome ('return a local preview'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'download_scihub_paper' or 'extract_local_pdf_text' which might have overlapping functionality, preventing a perfect score.

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 no guidance on when to use this tool versus alternatives like 'download_scihub_paper' or 'extract_local_pdf_text'. It mentions 'open-access PDF' but doesn't clarify what qualifies as open-access or when other tools might be more appropriate, offering minimal usage context.

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