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

No annotations are provided, so the description carries the full burden. '(streamed)' vaguely gestures at a streaming/NDJSON response, but it does not disclose chunking behavior, whether results arrive incrementally, ordering, or result-set limits — all of which matter for a streaming endpoint.

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?

Five words, front-loaded verb+resource with the differentiator in parentheses and zero filler. Its brevity is appropriate in form even though the content is thin.

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 annotations and no output schema, the description must explain the streaming contract, but it only alludes to it. An agent cannot tell what it will receive (NDJSON lines? chunks?) or how this differs operationally from tanks_search.

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%: 'q' is documented as a search prefix and 'region' has an enum of eu/na/asia, both required. The description adds nothing beyond the schema, so the baseline 3 applies.

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 clear verb+resource ('Search tanks') and the parenthetical '(streamed)' signals the one trait distinguishing it from the sibling tanks_search. However, it never explains what 'streamed' means or why an agent would pick this over the plain search, so sibling differentiation is only hinted at.

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?

There is no when-to-use guidance at all. With tanks_search sitting right next to it in the sibling list, the definition gives no condition, dataset size threshold, or alternative routing to explain when the streamed variant is preferred.

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