download_pubmed

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

The description discloses that the return is a failure message, but contradicts itself by claiming an 'attempt to download' while the return indicates no download occurs. Without annotations, the description should provide more accurate behavioral details.

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 uses a docstring format with Args and Returns, making it structured and moderately concise. Some redundancy could be removed.

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?

The description fails to explain the tool's core failure behavior—it claims to download but returns a message that download is not supported. This is incomplete for a tool that effectively does nothing, despite having an output schema.

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 coverage is 0%, but the description explains both parameters: paper_id is a PubMed ID and save_path is a directory with default './downloads'. This adds essential 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 clearly states the tool attempts to download a PDF from PubMed, distinguishing it from siblings for other sources. However, the return message indicates direct download is not supported, creating confusion about the actual purpose.

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 guidance is provided on when to use this tool vs alternatives, nor does it mention that the download typically fails, which would be critical for an agent to decide.

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