Export run evidence

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

Annotations (readOnlyHint=true, destructiveHint=false, openWorldHint=true) already indicate a safe read operation. The description adds valuable detail: bundle contents, 'private' nature, and 'paper trading only' — going beyond annotation hints without contradiction.

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?

Four sentences, each with specific information. No fluff. Front-loaded with the core action and resource.

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 read-only export tool with output schema present, the description adequately covers purpose, contents, privacy, and usage context (paper trading). No missing elements.

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 100%, so base is 3. The description mentions 'specific agentTrace.runId' but does not add new information beyond the schema's field descriptions for runId or agentTrace.

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?

Clearly states the verb 'Export' and the resource 'private reproducibility bundle for a specific agentTrace.runId'. Lists contents (sanitized ledger rows, etc.) and distinguishes from siblings like export_agent_ledger by specifying the bundle's uniqueness.

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?

Provides context: 'No public Arena user can see this data. Paper trading only — virtual funds (50,000 mUSD). Not financial advice.' This helps the agent know when to use it (paper trading) and privacy implications, but does not explicitly mention alternatives or when not to use.

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