Exa MCP Server

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds some behavioral context: 'performs real-time web searches,' 'can scrape content from specific URLs,' and 'returns the content from the most relevant websites.' This provides useful operational details beyond annotations, though it doesn't cover aspects like rate limits or authentication needs.

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 appropriately sized and front-loaded, with two sentences that efficiently convey core functionality. The first sentence covers the main purpose and key features, while the second adds result and content details. There's no wasted text, though it could be slightly more structured for clarity.

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's moderate complexity (5 parameters, no output schema) and rich annotations, the description is somewhat complete but has gaps. It explains what the tool does and some behavioral traits, but lacks usage guidelines and detailed output information. Without an output schema, the description doesn't clarify return values (e.g., format, structure), which is a notable omission.

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%, with all parameters well-documented in the schema (e.g., query, numResults defaults, livecrawl modes). The description adds minimal parameter semantics, mentioning 'configurable result counts' and implying content return, but doesn't provide syntax or format details beyond the schema. This meets the baseline of 3 for high schema coverage.

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's purpose: 'Search the web using Exa AI - performs real-time web searches and can scrape content from specific URLs.' It specifies the verb ('search'), resource ('web'), and key capabilities (real-time search, URL scraping). However, it doesn't explicitly differentiate from sibling tools like 'deep_search_exa' or 'crawling_exa', which appear related.

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 provides no guidance on when to use this tool versus alternatives. It mentions capabilities like configurable results and content scraping, but doesn't specify scenarios, prerequisites, or exclusions. With multiple sibling tools (e.g., 'deep_search_exa', 'crawling_exa'), this lack of differentiation is a significant gap.

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