get_all_tanks

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

Discloses that it returns all tanks the user has access to, implying user context scoping. No annotations provided, so description covers basic behavior. Could mention if there is pagination or caching but adequate for a simple list.

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?

Four sentences with clear purpose and instructions. Could be slightly more concise but no wasted words. Important usage guidance is included.

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?

Tool has no params and output schema exists, so description need not detail return values. It mentions 'basic information' which is vague but output schema fills that gap. Adequately complete for a list tool.

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?

No parameters, so baseline 4 applies. Schema coverage is 100% (empty schema). Description does not need to add parameter info.

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?

Description clearly states it fetches all tanks and provides basic information. Differentiates from get_single_tank_detail by mentioning it returns all tanks and can be used to find IDs for that tool.

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?

Explicitly states when to use: whenever user asks what tanks exist or about tanks in general. Also provides guidance on using it to get IDs for get_single_tank tool, and warns not to reveal IDs.

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