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

With no annotations, the description must disclose behavior. It mentions keyless access, cost per call, and parameter ranges, but does not explicitly state the operation is read-only or describe rate limits/error handling. It provides some behavioral context but not comprehensive coverage.

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 paragraph that efficiently packs purpose, return fields, use cases, cost, params, and an example. It is front-loaded with the purpose and reasonably concise, though a more structured layout could improve readability.

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?

There is no output schema, so the description should describe the return structure. It lists the returned fields but does not specify the response format (e.g., array of objects) or pagination behavior. For a search tool with no schema, this is a notable gap, though the core information is present.

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 schema only defines a generic 'params' object with no properties, so the description must define parameters. It does so thoroughly: name, maxItems, top_works, with ranges and an example. This fully compensates for the schema's lack of detail.

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 performs author and researcher profile search, specifies the returned data (affiliation, publication count, citations, h-index, i10-index, most-cited papers), and names explicit use cases (author lookup, disambiguation, citation-metrics). This is a specific verb+resource and differentiates from paper-centric sibling tools.

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 identifies when to use the tool via use cases (author lookup, disambiguation, citation-metrics) and notes the keyless OpenAlex source. However, it does not explicitly mention alternatives or when not to use it, though the sibling tools are mostly paper-related so the context is reasonably clear.

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