get_single_tank_detail

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

No annotations provided, so description must disclose all behavioral traits. It only says 'fetches detail and context' without describing side effects, auth requirements, or error conditions. The instruction about not revealing the primary key is agent behavior, not tool behavior.

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?

First two sentences are repetitive ('fetches the detail' and 'provides details and context'). Includes unnecessary instructions about user knowledge. Could be more concise without losing key 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?

Given the tool's simplicity (one param, output schema exists), the description covers essential usage but lacks error handling details and does not mention read-only nature. Adequate but not comprehensive.

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 has 0% description coverage, so description must compensate. It explains how to obtain the parameter (via get_all_tanks) but does not describe the parameter's meaning or constraints beyond what the schema title provides.

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?

Clearly states it fetches detail for a single tank, distinguishes from sibling 'get_all_tanks' which lists all tanks, and explicitly says 'Use this tool to get information on a tank whenever a user asks you about a specific tank.'

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?

Provides explicit when-to-use ('whenever a user asks about a specific tank'), alternative ('use get_all_tanks to find IDs'), and a strict rule ('never reveal the primary key').

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