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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether the tool requires authentication, what it returns, whether results are paginated, cached, or rate-limited.

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 text is short, but this is under-specification rather than conciseness: two words cannot be front-loaded or structured around anything. It fails to earn its place because it conveys almost no information.

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 bare fragment of a description, an agent has nothing to go on beyond a single required region enum. This is completely inadequate for a tool sitting among dozens of overlapping tank endpoints.

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?

There is one parameter (region) with 100% schema description coverage, including a clean enum, so the schema fully documents the input. The description adds no meaning beyond the schema and does not hint at how region affects the results, which is the baseline 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?

The description is a two-word fragment, "Tanks performance", that names the resource but supplies no verb and no clear action. It does not distinguish this tool from the many siblings covering tank data (tanks_ratings, tanks_economics, tanks_specifications, tanks_search), so an agent cannot tell what operation it performs.

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 guidance whatsoever on when to use this tool, when not to, or which sibling to prefer. With ~85 sibling tools and multiple plausible tank-related endpoints, the absence of routing information makes correct selection nearly impossible.

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