all_evidence_summary

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

The description reveals that the tool collects the complete streaming response before returning, indicating it aggregates an async stream. However, since no annotations are provided, the description carries the full burden and does not cover permissions, side effects, or rate limits.

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, concise sentence that front-loads the key action and important behavioral detail (streaming response collection).

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?

With no parameters and no output schema, the description adequately explains the tool's purpose and behavior. It could optionally clarify what 'all evidence' refers to or the expected output format, but it is sufficient for an agent to select this tool.

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?

The tool has zero parameters, so the description's meaning about the tool's purpose and behavior adds sufficient value beyond the empty schema.

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 retrieves a single AI summary of all evidence, and mentions the streaming response behavior, which distinguishes it from sibling tools like evidence_summary.

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 does not specify when to use this tool versus alternatives like evidence_summary or answer_stream, nor does it provide guidance on prerequisites or context.

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