spraay_research_papers_by_author

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds cost per call and source (OpenAlex), but does not disclose behaviors like pagination, error handling, or what happens when both author and orcid are provided. Value added beyond annotations is moderate.

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 concise, front-loading purpose, then cost and usage notes. It avoids fluff but could be more structured (e.g., bullet points). Still efficient and clear.

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 existing annotations and output schema, the description covers main purpose and cost, but omits pagination behavior, optionality of parameters, and potential error cases. Adequate for simple tool but not fully comprehensive.

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 descriptions are minimal ('page parameter'). The description says to pass fields directly, but fails to clarify format (e.g., full name vs. fragment, ORCID URI format) or the relationship between 'author' and 'orcid' (e.g., are they mutually exclusive?). The description adds insufficient meaning beyond the 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 tool retrieves papers by author name or ORCID from OpenAlex, distinguishing it from siblings like spraay_research_papers_by_doi (by DOI) and spraay_research_papers_search (general search).

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 mentions cost and read-only nature, but does not explicitly guide when to use this tool vs other paper-related siblings (e.g., by author vs search vs trending). It provides basic context but lacks exclusionary guidance.

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