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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing — no data scope, no whether this is aggregate vs per-tank, no auth or rate-limit notes. The two-word phrase conveys zero behavioral signal.

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 short, but this is under-specification rather than conciseness — there is no front-loaded statement of purpose or scope for a sentence to earn its place within. The phrase is a label, not a usable description.

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 an opaque name, the description leaves the agent unable to know what data this returns or how it differs from tanks_by_slug_economics. It is completely inadequate for a tool the agent must choose among ~90 siblings.

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 an enum and 100% schema description coverage, so the schema fully documents it. The description adds no extra meaning, which matches the baseline 3 for high-coverage schemas.

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 'Tanks economics' merely restates the tool name and supplies no verb or scope. It is a tautology, and it does not distinguish this tool from the sibling tanks_by_slug_economics, which appears to cover overlapping subject matter.

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?

No when-to-use, when-not-to-use, or alternative guidance is offered. With a near-identical sibling (tanks_by_slug_economics) in the toolset, the absence of any routing information is especially costly.

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