elba_get_contractor

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only hints at read semantics via 'карточка'. It says nothing about error behavior for a missing/invalid contractor_id, whether the call is safe/non-mutating, or what the returned contact data looks like beyond the word 'контактами'.

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 a single short phrase with no filler, so it is not verbose. But the brevity comes at the cost of substance, so the terseness reads as under-specification rather than disciplined concision.

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 output schema, no annotations, and an undescribed parameter, the description needed to compensate and does not. It leaves unclear what fields are returned, whether contacts are always present, and how the ID should be sourced.

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 description coverage is 0% and the single parameter contractor_id is undocumented in both schema and description. The description does not say whether the ID is the internal Elba identifier (as opposed to INN, which elba_lookup_inn handles), which is a meaningful ambiguity for this tool family.

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 phrase 'Карточка контрагента с контактами' indicates it retrieves a contractor record along with contact details, which is more than a tautology. However, it never states the retrieval verb explicitly and does not differentiate it from the sibling elba_find_contractor, so an agent cannot tell from the text alone which of the two to call.

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?

There is no guidance on when to use this versus elba_find_contractor (search) or elba_create_contractor. No prerequisites, no statement about needing an existing ID, and no exclusions are given; the agent must infer everything from the tool name.

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