OpenAlex Author Disambiguation MCP Server

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

Annotations provide readOnlyHint=true and openWorldHint=true, which the description doesn't contradict. The description adds useful context about the return format ('Serialized OptimizedSearchResponse with streamlined author data') and default/max values for limit parameter, which goes beyond what annotations provide. However, it doesn't mention rate limits, authentication needs, or pagination behavior.

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?

Well-structured with clear sections (Args, Returns). Every sentence adds value: the first establishes purpose, parameter descriptions are efficient, and return statement is specific. No wasted words or redundant information.

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 has annotations (readOnlyHint, openWorldHint) and an output schema exists, the description provides adequate context. It covers all parameters meaningfully and describes the return format. However, it could better differentiate from sibling tools and explain what 'optimized' means in practice.

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?

With 0% schema description coverage, the description carries full burden. It provides clear explanations for all 5 parameters including optional status, default values, and constraints (limit default:15, max:100). The description adds meaningful context about what each parameter filters, though it could provide more detail about format expectations (e.g., country_code 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?

The description states it's for 'searching authors' which is clear but vague. It doesn't specify what makes this 'optimized' or how it differs from sibling tools like 'search_orcid_authors' or 'search_pubmed'. The description mentions 'streamlined author data' but doesn't clarify what that means compared to other search 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?

No guidance on when to use this tool versus alternatives like 'search_orcid_authors', 'search_pubmed', or 'autocomplete_authors'. The description mentions it's 'optimized' but doesn't explain what optimization means or in what contexts it should be preferred over other search tools.

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