Paper Pilot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the Sci-Hub fallback behavior, which is useful context, but doesn't describe other critical behaviors like rate limits, authentication needs, what happens during download/extraction, or the format of returned evidence chunks. For a complex tool with 18 parameters, this leaves significant gaps.

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 appropriately concise with two sentences that efficiently convey core functionality and one key parameter behavior. It's front-loaded with the main purpose, though it could be slightly more structured given the tool's complexity.

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 complex tool with 18 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'evidence chunks' are, how results are structured, what happens with Zotero integration, or provide guidance on parameter interactions. The agent would struggle to use this tool effectively without additional documentation.

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?

With 0% schema description coverage and 18 parameters, the description fails to compensate for the lack of parameter documentation. It only mentions one parameter ('include_scihub') and provides no context about what the other 17 parameters do, their relationships, or typical values. This leaves most parameters semantically undefined.

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 tool's purpose with specific verbs ('Search, download, extract full text, and return evidence chunks plus local PDF paths') and identifies the resource ('papers'). However, it doesn't explicitly differentiate from sibling tools like 'research_topic' or 'search_literature', which likely have overlapping functionality.

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 some implied usage guidance by mentioning the Sci-Hub fallback feature, suggesting it's for accessing papers that may not be openly available. However, it lacks explicit guidance on when to use this tool versus alternatives like 'research_topic' or 'search_literature', and doesn't mention prerequisites or exclusions.

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