find_papers_by_author

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

With no annotations provided, the description carries the full burden. It mentions 'recent' and 'sources like arXiv,' but fails to disclose search match behavior, rate limits, error handling, or return format. This is minimal behavioral disclosure for a search tool.

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 front-loaded with a concise, actionable sentence followed by a tight args list. Every word earns its place; no extraneous content.

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?

The tool is simple (2 params, no output schema), but the description omits return value details and usage guidance relative to sibling tools. Given no annotations and no output schema, the lack of behavioral and return information makes it slightly incomplete, though usable.

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 description coverage is 0%, so the description must compensate. The 'Args' section fully explains both parameters: author_name with an example ('Geoffrey Hinton') and max_results with its default. This adds clear 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 'Finds recent academic papers by a specific author's name from sources like arXiv,' using a specific verb and resource. It distinctively positions this tool as author-based lookup, differentiating it from siblings like search_papers and get_paper_by_id.

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 usage for author-based paper searches but does not explicitly contrast with sibling tools such as search_papers or get_latest_from_category. It lacks when-not-to-use guidance, so it only provides implied usage context.

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