read_ssrn_paper

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

With no annotations provided, the description carries the full burden. It transparently discloses that the tool returns an error message because SSRN is metadata-only, and that the save_path parameter is unused. This clearly communicates the tool's behavior and limitations.

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 and front-loaded, with the main action stated first, followed by a crucial note. The Args and Returns are clearly formatted. However, the first sentence alone is misleading without the note, slightly reducing conciseness effectiveness.

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 that the tool always returns an error string, the description covers the essential behavior. However, it does not specify the exact error message format or whether other errors (e.g., invalid paper_id) could occur. The output schema is not shown, so the return type is vaguely described.

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?

The description adds meaning to both parameters: paper_id is described as 'SSRN paper identifier' (schema says 'Paper Id'), and save_path is noted as 'Directory where the PDF is/will be saved (unused)'. Since schema description coverage is 0%, the description compensates but the explanations are minimal, lacking format details for paper_id.

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 'Read paper content from SSRN' which clearly identifies the intended action and resource. It immediately follows with a note that the SSRN connector is metadata-only and read is not supported, clarifying that the tool returns an error. This distinguishes it from other read_* tools that actually return content.

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 no explicit guidance on when to use this tool vs alternatives. While it states that reading is not supported, it does not recommend using download_ssrn or other tools. The note implies this tool is not useful for acquiring content, but fails to direct the user to a viable alternative among siblings.

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