search_ssrn

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

Discloses metadata-only limitation and no PDF download, which is valuable beyond schema. No annotations provided, so description carries burden; but lacks details on rate limits, authentication, or error handling.

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?

Concise with front-loaded purpose, followed by limitation note and structured argument documentation. No unnecessary sentences.

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 output schema exists and tool is simple (2 params), description covers purpose, limitation, parameters, and return type. Could mention pagination, but not critical for this tool.

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 coverage, description explains 'query' as search query string and 'max_results' as maximum papers to return with default 10. This adds meaningful context beyond the schema's types and defaults.

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?

Description clearly states 'Search metadata records from SSRN', using a specific verb and resource. It distinguishes from sibling search tools by noting it's metadata-only and no PDF download.

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?

Explicitly notes SSRN connector is metadata-only and does not support direct PDF download, guiding agents to use download tools for PDF retrieval. Could be more explicit about when to search vs. read or download alternatives.

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