download_ssrn

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

The description explicitly states that the connector is metadata-only and download is not supported, and that the return is an error message. This clearly discloses the tool's behavior (always fails) despite the misleading name. With no annotations, the description carries the full burden and does well here.

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 short but contains contradictory statements (download vs. not supported). This creates confusion and reduces effectiveness. While it front-loads the purpose, the contradiction undermines conciseness. A clearer structure would be better.

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 low complexity (2 params, no annotations) and presence of an output schema, the description adequately explains the behavior (always error) and the unused param. However, it does not mention that the tool is essentially a placeholder or provide a reason for its existence, leaving some gaps.

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 add meaning. It describes paper_id as 'SSRN paper identifier' (minimal) and save_path as 'Directory to save the PDF (unused)' which adds value by indicating the parameter is ignored. However, it does not provide format or constraints, so it is adequate but not exceptional.

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 'Download PDF for a paper from SSRN' but immediately contradicts with 'SSRN connector is metadata-only and download is not supported'. The actual purpose is to return an error message, not to download. This is misleading and unclear.

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 on when to use this tool. It does not mention that the download will fail, nor does it suggest alternatives like using the 'read_ssrn_paper' or other download tools. The description provides no context for appropriate use.

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