check_inn

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

No annotations are provided, so the description carries full burden. It describes the output as a 'full card' but does not disclose behavioral traits such as auth requirements, rate limits, or side effects. The description adds minimal behavioral context beyond the input format.

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 a single, well-structured sentence that front-loads the main purpose. Every word adds value, with no filler. It is appropriately concise.

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 that an output schema exists, the description does not need to detail return values. However, the description is terse and does not specify what the 'full card' includes, leaving some ambiguity. It adequately covers the basic purpose but could be more 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 description coverage is 100%, so baseline is 3. The description adds meaningful context for the 'inn' parameter by specifying the digit length for legal entities vs IPs. For 'include_extended', it clarifies it is reserved for future use, adding value beyond the schema.

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 returns a full counterparty card by INN, and specifies the length distinction (10 digits for legal entities, 12 for individual entrepreneurs). This is a specific verb and resource, and it helps distinguish from sibling tools like check_ogrn (which checks OGRN).

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 implies usage for obtaining a counterparty card based on INN but does not explicitly state when to use this tool versus alternatives like check_contractor or check_for_red_flags. No when-not conditions or alternative recommendations are provided.

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