author_search

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

No annotations provided, so description carries full burden. States it returns matching profiles but does not disclose search algorithm (exact match, fuzzy, partial), result ordering, or pagination behavior. Minimum viable but lacks depth.

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?

Two sentences, no redundant information. Front-loaded with action and resource. Every sentence earns its place.

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?

5 parameters with no output schema or annotations. Description is minimal; does not explain return format, default fields, or pagination hints. Could be more complete given the fields parameter complexity and lack of output schema.

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 100%, so baseline 3. Description only mentions high-level return fields (h-index, paper count, affiliation) but does not add meaning beyond schema for individual parameters like fields, offset, or response_format.

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?

Clearly states verb 'Search', resource 'authors', and search criteria 'by name'. Specifies returned data: 'matching author profiles with h-index, paper count, and affiliation.' Distinguishes from sibling tools like author_get and author_batch which retrieve 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?

Implies usage for name-based search, but lacks explicit guidance on when to use this tool vs alternatives like author_get or author_batch. No when-not-to-use or prerequisite conditions mentioned.

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