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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral trait, 'точное совпадение' (exact match, no fuzzy matching), but says nothing about the result shape or how a match is reported.

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 filler; the registry identity and match semantics come first. It is terse rather than padded, though it could afford one more clause about output.

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 no output schema, the description carries the burden of explaining what a check returns (found/not found, any associated data), and it does not. For a screening tool feeding compliance decisions, that is a noticeable gap, though the input contract is fully covered.

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 all four parameters are documented in the schema itself. The description restates the same input tuple (ФИО + год рождения) without adding format, normalization, or matching-rule detail beyond 'exact'. Baseline 3 applies.

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?

Names a specific verb (Проверка), resource (реестр иностранных агентов Минюста РФ), and entity type (физлица), which implicitly separates it from the sibling check_inoagent_org. It does not explicitly name that sibling, so it falls just 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 description gives no when-to-use guidance or alternatives; the exact-match requirement and the input combination are implied by the parenthetical. An agent can infer this is a name-based screening check, but routing versus check_sanctions_person or check_fedsfm_person is left to the tool name alone.

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