get_account

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

No annotations are provided, so the description carries the full burden. It states that the tool returns an account record with fields like name, dealerCode, phone, etc. However, it does not disclose error behavior (e.g., what happens if account_id does not exist), permissions, or any side effects. For a read operation, basic safety is implied but not explicit.

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?

Three sentences, all essential. The first states purpose, the second provides usage context, the third gives an example. No fluff, front-loaded. Ideal conciseness.

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 parameter, straightforward fetch) and the existence of an output schema (not shown), the description covers the main aspects. It could mention error handling or missing account cases, but for a basic lookup, it is largely sufficient.

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?

The input schema has one required integer parameter, account_id. The description adds an example 'account_id=1042 returns account record', which provides context on how the parameter is used. However, schema description coverage is 0%, meaning the schema itself has no descriptions; the description compensates partially but does not detail constraints or valid ranges.

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 clearly states 'Fetch one dealer account by id.' It uses a specific verb (fetch), identifies the resource (dealer account), and specifies the method (by id). This distinguishes it from sibling tools like list_accounts and iter_accounts.

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 includes explicit use cases: 'Use when: "what's the phone number for dealer 1042?" or "show me account 1042".' It also provides an example with input and output. It does not explicitly state when not to use, but the singular retrieval context is clear.

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