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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully adds that matching is by full name plus year of birth and is an exact match, but says nothing about what is returned or how a hit is represented.

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 with no padding; the list name and the matching rule are the only two facts given and both earn their place. It is slightly terse for a screening tool, keeping it from a 5.

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 safety covered by annotations and no output schema to explain, the description gives the essentials: what is checked and how matching works. It omits how negative versus positive results are surfaced, which would be the only remaining helpful addition.

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%, so individual parameters are already documented (baseline 3). The description adds meaning beyond the schema by stating that the four fields (ФИО + год рождения) are combined and that matching is exact, clarifying how the parameters must be supplied together.

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 (проверка/check), a specific resource (физлицо/individual), and the exact list (Росфинмониторинг terrorists/extremists). The word 'физлицо' implicitly separates it from check_fedsfm_org, but no sibling is named explicitly, so it falls short of a 5.

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 stated scope (individual + terrorist/extremist list) implies when the tool applies, but there is no explicit when-to-use, no exclusions, and no reference to alternative person-screen tools such as check_sanctions_person or check_mvd_wanted. Usage is left to inference.

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