download_ssrn

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

With no annotations provided, the description carries the full burden. It discloses critical behavioral traits: the tool is metadata-only (implying it won't actually download PDFs), the save_path parameter is unused, and it returns an error message. This covers key limitations and expected outcomes, though it lacks details on rate limits, authentication needs, or specific error conditions.

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 and front-loaded with the main purpose, followed by a critical note and clear parameter/return explanations. Every sentence adds value: the first states the intent, the second warns of limitations, and the subsequent lines detail inputs and outputs without redundancy. It's appropriately sized for 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?

Given the tool's complexity (simple parameters but critical behavioral limitations), no annotations, and an output schema present (implied by 'Returns: str'), the description is largely complete. It covers purpose, limitations, parameter semantics, and return values. However, it could improve by mentioning sibling tools or error-handling specifics, though the output schema reduces the need for detailed return explanations.

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 explains that 'paper_id' is an SSRN paper identifier and 'save_path' is a directory to save the PDF but is unused. This adds meaningful context beyond the schema's basic titles and types, clarifying parameter roles and limitations. However, it doesn't specify format constraints (e.g., paper_id structure) or provide examples.

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 states the tool downloads PDFs from SSRN, which is a clear verb+resource combination. However, it doesn't differentiate from sibling tools like 'download_arxiv' or 'download_biorxiv' beyond specifying the SSRN source. The note about metadata-only limitations adds specificity but doesn't fully distinguish it from similar download tools for 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?

The description provides explicit guidance about when NOT to use this tool ('SSRN connector is metadata-only and download is not supported'), which is valuable context. However, it doesn't mention when to use this tool versus alternatives like 'read_ssrn_paper' or other download tools for different repositories, nor does it provide prerequisites or error handling advice beyond the return statement.

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