download_zenodo

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

The description merely states the basic operation without disclosing behaviors like error handling, file overwrite policy, or rate limits. No annotations exist to fill the gap.

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 concise with a clear purpose statement and separate parameter docs. No unnecessary words.

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 covers the return type and default save path, but lacks details about naming conventions, overwrite behavior, and error responses. Given the existence of an output schema, some completeness is acceptable.

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?

The description explains the purpose of both parameters ('paper_id: Zenodo paper identifier', 'save_path: Directory to save the PDF'), adding value beyond the schema which only provides titles. However, it does not clarify the expected format of paper_id.

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 PDF'), the specific resource ('paper'), and the source ('Zenodo'). It distinguishes from sibling tools that target other repositories.

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 over alternatives (e.g., other download_* tools for different sources). The description does not mention prerequisites or context.

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