read_user_messages

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

With no annotations, the description carries the full burden and largely meets it: it discloses the read is capture-free, the wire envelope `cb 53 9a <byte-len> <UTF-8>`, the return shape, and honestly flags that multibyte Cyrillic decoding is unproven. Remaining gaps (permissions, error behavior) are minor for a read tool.

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?

Front-loads the purpose in the first sentence and keeps every subsequent clause informative (envelope format, return shape, caveat). It is dense and jargon-heavy, but the length is largely justified by the tool's low-level nature.

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?

An output schema exists, yet the description usefully still names the return keys; combined with the behavioral and protocol details it gives an agent enough to invoke the tool correctly. Only the unexplained `host`/`port` and absent permission/error notes are minor gaps.

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 compensate. It explains `expected` (assert a message is present) and gives some meaning to `capture` ('the genuine flow from `capture`'), but leaves `host` and `port` undocumented beyond convention. Partial compensation, not full.

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?

Opens with a specific verb+resource: 'Read the user messages a form emits', and further pins its function as 'the capture-free ASSERTION read' for «нет сообщений пользователю» and `Сообщить` output. This is far more precise than a tautology, though it does not explicitly name a sibling tool it must not be confused with.

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?

States the concrete contexts for use: asserting 'нет сообщений пользователю' and reading `Сообщить` output, plus the `expected` mechanism for asserting a specific message. It gives clear positive guidance but names no alternative tool or explicit when-not condition.

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