tochka_account_detail

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

Annotations already declare readOnlyHint=true, so the description adds some value by specifying the default behavior (uses first account if account_id empty). However, no other behavioral traits are disclosed beyond that, such as concurrency, rate limits, or side effects. The description does not contradict annotations.

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 description is extremely concise—two sentences with no wasted words. The purpose is front-loaded in the first sentence. Every sentence adds value without redundancy.

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 existence of an output schema, the description does not need to explain return values. It adequately covers the only parameter and the tool's basic purpose. However, it could mention that this is for a specific bank account system or note any prerequisites (e.g., authentication), but overall it is sufficiently complete for a simple read tool with good annotations.

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?

With 0% schema description coverage, the description compensates well by explaining the 'account_id' parameter with an example format and noting the default empty-string behavior. This adds significant meaning beyond the schema, though it could have provided more detail about allowed formats or constraints.

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 the tool gets 'detailed account information', which is a specific resource. It uses a specific verb 'Get' and resource 'detailed account information', but does not explicitly differentiate from sibling tools like 'tochka_balance' or 'tochka_all_balances', which limits clarity slightly.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention circumstances under which this tool is preferable, nor does it list when not to use it. The only usage hint is about using the first account if account_id is empty, but this is more behavioral than comparative.

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