Exa Agent run status/result

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that wait=true polls until completion or waitSeconds, but it omits other behavioral details such as cache behavior, token cost of raw output, and error conditions.

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?

A single compact sentence with the core operation front-loaded and no wasted wording. It efficiently conveys the id lookup and the optional polling behavior.

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 tool with no output schema and no annotations, the description is somewhat thin. It covers the core get-by-id and wait behavior, but it does not describe what the run result contains or how status/result data is returned.

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 coverage is 50%, and the description compensates by explaining the important wait and waitSeconds semantics. The remaining parameters are either self-explanatory or documented in the schema, though the description does not add meaning for raw, noCache, or maxChars.

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: get an Exa Agent run by id. It is clearly a retrieval tool, but it does not explicitly distinguish itself from siblings like exa_agent_run or exa_agent_manage.

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 implies usage by saying to get a run by id and explains the wait=true polling behavior. It does not state when to use this versus exa_agent_run or exa_agent_manage, nor does it give exclusions.

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