generate_batch_report

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

No annotations are provided, so the description carries the full burden. It adds useful context by noting that analysis happens 'concurrently' and that the result is a 'combined report' with specific metrics. However, it does not explicitly state whether the operation is read-only, the nature of the report structure, or any potential side effects or limitations (e.g., rate limits, failure handling).

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 sentence that is front-loaded with the action ('Concurrently analyze') and resource ('multiple trader profiles'), followed by the output contents. Every word contributes, with no redundancy or filler.

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 absence of an output schema, the description should clarify what the 'combined report' looks like (e.g., per-profile breakdown vs. aggregated summary) and any edge cases. It lists key fields but leaves structural ambiguity about how results are organized, making it minimally complete but not fully self-sufficient.

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% for the single parameter profile_ids, with a clear description in the schema. The tool description merely echoes 'multiple trader profiles,' adding little beyond the schema's 'Array of profile IDs (wallet addresses or usernames).' Thus the baseline of 3 is appropriate.

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 function: 'Concurrently analyze multiple trader profiles and generate a combined report' with specific output components (PnL, risk, score, bot status). This distinguishes it from sibling tools like analyze_trader_strategy (single profile) and find_top_traders (discovery).

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 phrase 'multiple trader profiles' implies a batch use case, but it does not explicitly contrast with analyzing profiles individually via analyze_trader_strategy, nor does it state conditions for when this tool is preferred. Usage context is only implied, not explicitly guided.

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