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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds genuine behavioral scope beyond that: a result cap (up to 100 latest notices) and the role condition (organization as customer OR participant). Return format and empty-result behavior remain undescribed, keeping it short of a 5.

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?

A single, front-loaded sentence that packs source, filter, result limit, and role scope with zero filler. Nothing is wasted.

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 a single parameter, full annotation coverage, and no output schema, the description supplies the essential context: data source, filter, result cap, and role scope. It could note whether an empty list is possible or that the org must exist in EIS, but it is largely complete for this simple lookup.

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?

The single parameter has 100% schema description coverage, including the 10/12-digit format, so the schema carries the semantics. The description adds no syntax or format detail beyond what the schema provides, matching the baseline 3 for high-coverage cases.

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 names a specific resource and data source (procurement notices of EIS / zakupki.gov.ru) filtered by INN, and states the scope of the result set. The verb is implicit (retrieve/list) rather than explicit, but an agent can immediately tell what data this returns. No sibling covers procurement notices, so no sibling differentiation is required.

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?

Usage is implied by the purpose (checking an organization's procurement activity via its INN) but there is no explicit when-to-use statement and no named alternatives or exclusions. Since no sibling overlaps with this data source, the gap is mild, but the description does not actively guide selection.

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