read_ssrn_paper

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

With no annotations provided, the description carries full burden and excels at behavioral disclosure. It explicitly states the tool's limitation ('metadata-only and read is not supported'), reveals what the tool actually does (returns an error message), and explains parameter behavior ('save_path' is 'unused'). This provides crucial context beyond basic functionality.

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 perfectly structured and front-loaded: the core purpose is stated first, followed by a critical note, then parameter explanations, and finally return value information. Every sentence earns its place with zero waste, making it highly efficient for an agent to parse.

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 (it essentially always fails with an error message), no annotations, and 0% schema coverage, the description provides complete context. It explains the tool's actual behavior, parameter usage, and return value, and the output schema exists (confirming the string return type), making this description fully adequate for the agent's needs.

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?

With 0% schema description coverage and 2 parameters, the description fully compensates by explaining both parameters: 'paper_id' is identified as 'SSRN paper identifier' and 'save_path' is explicitly noted as 'unused' with context about its purpose ('Directory where the PDF is/will be saved'). 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 action ('Read paper content from SSRN') and identifies the resource ('SSRN paper'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'download_ssrn' or 'search_ssrn' beyond the 'read' action, which is why it doesn't reach a perfect score.

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 usage guidance with the note: 'SSRN connector is metadata-only and read is not supported.' This clearly indicates when NOT to use this tool (when expecting actual paper content) and sets expectations about its limitations, making it highly effective for guiding agent decisions.

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