check_contractor

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

No annotations are provided, so the description bears full responsibility. It discloses identifier validation logic and parameter defaults (extended risks, lawsuit threshold), but does not elaborate on what the 'full check' entails, side effects, or authentication requirements. The output schema exists but is not referenced.

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 concise (three sentences) with the main purpose front-loaded. Every sentence adds critical information: identifier formats, validation, and parameter defaults. No redundant or vague phrasing.

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 output schema, return values are covered. The description sufficiently explains input validation and parameter behavior for a 3-param tool. It does not mention prerequisites (e.g., API keys) or how this tool relates to siblings beyond being the 'main' one, but overall it is adequate for agent invocation.

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 100% schema coverage, the description adds significant value beyond the schema. It explains identifier format and validation rules, specifies what extended risks include (4 checks: transparent business, FSSP, KAD), and clarifies the lawsuit threshold filters small disputes. Default values are contextualized.

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 performs a full counterparty check using a single identifier (INN or OGRN). It specifies validation criteria (digit length, control digit) and implicitly differentiates from sibling tools (check_inn, check_ogrn) that only handle one identifier type.

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 advises when to use this tool (for a full check) and provides input validation rules. It does not explicitly state when to use alternatives or when not to use this tool, but the context of being the 'main tool' implies it is the default for comprehensive checks.

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