read_semantic_paper

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

No annotations are provided, so the description carries full burden. It mentions downloading and saving PDFs ('Directory where the PDF is/will be saved'), implying network and file system operations, but lacks details on permissions, rate limits, error handling, or whether it's read-only/destructive. The description adds some context but is insufficient for a tool with no annotations.

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 well-structured with clear sections (Args, Returns) and uses bullet points for paper_id formats. It is appropriately sized, but the long list of formats could be slightly condensed. Every sentence adds value, making it efficient.

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 an output schema (returns 'str'), the description does well by detailing parameters and the return value. However, it lacks behavioral context (e.g., network usage, errors) and sibling differentiation, leaving minor gaps for a tool with no annotations.

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. It provides comprehensive details on 'paper_id' formats (8 examples with prefixes) and explains 'save_path' as a directory for PDF storage with a default value. This adds significant 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 the tool's purpose with specific verbs ('Read and extract text content') and resource ('from a Semantic Scholar paper'). It distinguishes itself from sibling tools like 'download_semantic' and 'search_semantic' by focusing on content extraction rather than downloading or searching.

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 explicit guidance is provided on when to use this tool versus alternatives. With many sibling tools for different sources (e.g., 'read_arxiv_paper', 'read_pubmed_paper'), the description does not clarify when Semantic Scholar is preferred or what distinguishes it from other paper-reading tools.

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