download_semantic

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

With no annotations, the description carries full burden. It discloses that the tool downloads a PDF and returns its path, but lacks details on error handling (e.g., if paper not found or PDF unavailable) or side effects. Given the simple nature, it is adequate but not comprehensive.

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 and well-structured: a one-sentence purpose, followed by clear Args and Returns sections. It is front-loaded with the primary action and uses bullet-like formatting for parameter details without waste.

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 download tool with two parameters, the description covers purpose, parameters, and return value. It does not mention prerequisites (e.g., network access) or error scenarios, but the output schema likely mitigates the need for exhaustive return documentation. Sibling differentiation is absent, but overall adequate.

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%, yet the description thoroughly explains both parameters: 'paper_id' with eight allowed formats (e.g., 'DOI:10.18653/v1/N18-3011') and 'save_path' with default './downloads'. This provides essential meaning beyond the bare 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 'Download PDF of a Semantic Scholar paper' with a specific verb (download) and resource (PDF of a Semantic Scholar paper). It distinguishes from siblings like 'download_arxiv' and 'download_pubmed' by specifying the source as Semantic Scholar.

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 implicitly indicates usage by listing acceptable paper_id formats (Semantic Scholar ID, DOI, ARXIV, etc.), suggesting it works for multiple identifier types from Semantic Scholar. However, it does not explicitly compare to siblings or state when to use this tool over others like 'download_scihub' or 'download_pubmed'.

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