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

No annotations are provided, so the description bears the full burden. "Streamed" is a genuine behavioral disclosure about output delivery, but nothing explains what a streamed response means for the caller (incremental NDJSON lines, no pagination, how to terminate, error behavior mid-stream) or that this is a read-only operation. Sparse for a zero-annotation tool.

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?

It is only a few words with zero redundancy, and the resource name is front-loaded. But the brevity comes from omission rather than discipline — the parenthetical is doing unexplained work. Terseness that leaves the caller uninformed is not a conciseness win.

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?

There is no output schema, so the description would need to carry return-format information, and it does not. Combined with the missing guidance on clans_search vs this streamed variant, an agent lacks what it needs to choose correctly and to consume the streamed result.

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" (search prefix) and "region" (enum eu/na/asia) are fully documented in the schema itself. The description adds nothing about how prefix matching behaves or whether region affects result scope. Baseline 3 applies when the schema does the heavy lifting.

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?

It names a specific verb and resource ("Search clans") and the parenthetical "(streamed)" hints that output is streamed/NDJSON rather than a normal response. However, it never distinguishes itself from the sibling clans_search (nor players_search_ndjson / maps_search_ndjson / tanks_search_ndjson), so an agent must guess why both variants exist. Purpose is identifiable but not clearly scoped against alternatives.

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 explicit when-to-use guidance and no mention of the obvious alternative clans_search. The only implied routing signal is "streamed," which a caller must interpret on their own. For a tool that sits directly beside clans_search in the namespace, this is a real gap.

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