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

Annotations already cover readOnly, openWorld, idempotent, and destructive hints. The description adds the data source (api.semanticscholar.org) and explicitly states 'no auth required', which are useful behavioral disclosures beyond the annotations. It does not mention rate limits or pagination, but for a read-only search with annotations already declaring safety, this is adequate.

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 three sentences with no wasted words. It front-loads the purpose, then returns, then usage context, then data source. Every sentence earns its place, making it efficient and easy to scan.

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?

For a simple 2-parameter read-only search with full schema coverage, an output schema, and robust annotations, the description covers purpose, returns, use cases, data source, and auth. Nothing an agent needs to call it correctly is missing.

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% since both query and limit have descriptions. The description only reinforces that the query is for a display name, which the schema already conveys. It adds no additional parameter semantics beyond the baseline, so a 3 is appropriate.

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?

States a specific verb and resource ('Search researcher/author records by display name'), enumerates the return fields (author ID, name, affiliations, counts, h-index), and distinguishes itself from siblings by noting it serves as a pre-step to filtering semanticscholar.papers_search. An agent can immediately understand what this tool does and how it differs from related 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?

Gives explicit use cases: 'identifying a researcher before filtering semanticscholar.papers_search results by author' and 'author-level impact metrics'. This clearly routes the agent to the right sibling tool. It stops short of explicitly stating when not to use it, but the context is strong enough to guide selection.

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