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

The only annotation is readOnlyHint=false, and the description does not explain what the non-read-only effect is. It does not say whether this opens a dialog, consumes a turn, requires proximity, or what happens on failure.

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 a single compact sentence with the action and target front-loaded. The parenthetical about game_look adds useful context without waste.

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 one-parameter tool with no output schema, the core information is present. Still, an action tool in a dialog-heavy sibling set should clarify what 'talking' initiates and how it connects to conversation follow-up tools.

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%, so the description must carry parameter meaning. It usefully states that the npc value should be a name obtained from game_look, but it does not clarify expected format or matching behavior beyond that.

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 action ('Заговорить') and target ('NPC рядом'), and even points to game_look as the source of the NPC name. It is clear what the tool does, though it does not explicitly distinguish itself from dialog-related siblings such as game_dialog.

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?

It implies the NPC must be nearby and that the name should come from game_look, giving useful prerequisite context. However, it does not say when not to use it or how it relates to game_dialog/game_dialog_answer.

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