find_citations_by_authors

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

With no annotations, the description must explain behavior, but it only says 'find all publications.' This is misleading because the max_results parameter limits output, and the description omits details about response format, limits, or any side effects. It does not contradict annotations (there are none), but it provides very thin behavioral transparency.

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 a single sentence with no extraneous phrases. Every word contributes to conveying the core function, making it highly concise and well-structured for the purpose it serves.

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 (4 parameters, sibling search tools, no annotations), the description is too minimal. While an output schema exists to explain return values, the description fails to provide guidance on usage context, result limits, or how it differs from other search tools, leaving an agent under-equipped for correct selection and invocation.

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 input schema already describes all four parameters with 100% coverage, including the meaning of author_name, max_results, and the date range parameters. The description adds no parameter-level semantics beyond what the schema provides, so the baseline score of 3 applies.

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 finds publications by an author, with a specific verb ('Find') and resource ('publications', though the tool name says 'citations'). It does not explicitly differentiate from sibling tools like pubmed_search or advanced_search, but the author-specific scope makes its purpose distinct.

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 implies the tool should be used when you need publications by a specific author, but it provides no explicit guidance on when to use this tool versus the many search-oriented siblings (pubmed_search, pmc_search, etc.). There are no exclusions or direct comparisons.

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