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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: no read-only confirmation, no pagination or result-limit behavior, no rate-limit or response-shape notes. It is a pure restatement of the tool name.

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?

Two words are front-loaded and waste-free, but this is under-specification rather than conciseness: the text is too thin to orient an agent. Length is not the problem; the absence of substance is.

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, no output schema, and a confusingly similar ndjson sibling, the definition should at least clarify scope and result behavior. As written, an agent cannot tell this tool apart from tanks_search_ndjson or know what it returns.

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%, with both q ("Search prefix") and region (enum eu/na/asia) documented in the schema. The description adds no meaning 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?

"Search tanks" names a verb and a resource, so the agent knows it queries tanks by prefix. However it gives no scope or differentiation from close siblings such as tanks_search_ndjson or the plain tanks listing, leaving the agent to guess which search surface to use.

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 provides no when-to-use guidance, no exclusions, and no mention of the near-identical tanks_search_ndjson alternative. An agent must infer usage purely from the name.

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