check_tax_arrears

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

No annotations provided, so the description covers behavioral aspects: read-only HTTPS, requires Pro API key and token, returns structure. It lacks details on error handling or rate limits but is sufficiently transparent.

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 with three short paragraphs: purpose, usage guidelines, and return format. Every sentence adds value with no 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 simple tool (1 required parameter, no nested objects, output described), the description covers purpose, usage, requirements, and output adequately. Could mention error handling or data freshness but is largely complete.

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 coverage is 100% with schema description for 'inn'. The description adds usage context (10–12 digit INN, counterparty due diligence) beyond the schema's 'ИНН организации/ИП.', enhancing the parameter semantics.

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 checks tax arrears/debt flags from a specific data source, with a specific resource (INN). However, it does not explicitly differentiate from sibling check tools like check_account_block, though the domain (tax arrears) is distinct.

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?

Explicitly provides when-to-use (counterparty due diligence with specific INN length) and when-not-to-use (official certificate, offline), including an alternative. This fully meets the dimension criteria.

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