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

With no annotations, the description carries the full behavioral burden, and it does disclose a real trait: submissions are accepted into a queue in phase 1 with no live 1C invoice yet, implying an async/non-immediate outcome. It still omits idempotency, dedupe, permission/auth needs, and what the caller receives back or what happens next.

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?

Three short sentences, zero padding, and the core action plus key inputs are front-loaded. It is efficient, though the terseness is partly why it under-documents the parameter set.

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?

For a 12-parameter mutation tool with no annotations and 0% schema coverage, the description is too thin. An output schema exists, so return values need not be described, but the many optional fields and the queue/lifecycle behavior are left to inference.

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% across 12 parameters, so the description is the only documentation. It names reg_number, product_sku and loosely covers payer requisites, but leaves inn/kpp/ogrn, edo_id, delivery_channel (default 'email'), email, comment and contact fields entirely unexplained.

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?

States a specific verb+resource ('Request an invoice for ITS renewal'), making the action legible at a glance. It does not, however, distinguish itself from closely related siblings like quote_its_renewal or subscribe_its_renewal, so an agent must infer the boundary.

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 when-to-use guidance or alternatives are offered. The only contextual clue is the phase-1 queue note, which hints this is a preliminary submission step but never says when an agent should pick this over quoting or subscribing.

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