MCP Think Tank

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions sourcing via an API but doesn't cover critical aspects like rate limits, authentication needs, error handling, or what the output looks like (e.g., structured answer with citations). For a tool with external API calls and no annotations, this is a significant gap.

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, efficient sentence that directly states the tool's function without any wasted words. It's appropriately sized and front-loaded, making it easy to grasp quickly.

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 complexity of an external API tool with no annotations and no output schema, the description is incomplete. It doesn't explain the return format (e.g., how citations are structured), potential limitations, or error cases, leaving gaps for an agent to invoke it correctly in varied contexts.

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 the schema already documents both parameters ('question' and 'max_citations') with details like minLength, default, and range. The description adds minimal value beyond implying the question is for sourcing answers, but doesn't provide additional syntax or format insights beyond what the schema offers.

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 action ('Ask a question and get a sourced answer') and the resource/method ('via Exa /answer API'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'exa_search' or 'memory_query', which might also retrieve information, so it lacks sibling distinction for a perfect score.

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. With siblings like 'exa_search' and 'memory_query' that could serve similar information-retrieval purposes, there's no mention of context, prerequisites, or exclusions to help an agent choose appropriately.

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