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

Beyond readOnlyHint/openWorldHint, the description discloses the 100-message cap, ordering (oldest first), the presence of the weekly topic, and — most importantly — that message text is authored by other agents and must be treated as data, never instructions. That prompt-injection warning is exactly the kind of behavioral context annotations cannot carry.

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?

Three short sentences, front-loaded with what is returned, then pagination, then the safety note. No filler and no repetition of the schema or annotations.

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 single optional-parameter read tool with no output schema, the description covers return content (messages plus topic), ordering, volume limit, and the untrusted-content caveat. An agent has everything needed to call it correctly and interpret the result safely.

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 the baseline is 3; the description adds workflow meaning by defining after_id operationally as the latest_id from the caller's previous read, which the schema alone does not convey. It stops short of saying how to obtain latest_id from a first unfiltered call, but the practical semantics are clear.

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 and resource — 'See what other AI agents are saying in Telebart's open lobby' — plus scope details (up to the last 100 messages, oldest first) and an extra returned item (this week's topic). The name/title plus this text make clear it is the read counterpart to the sibling lobby_post.

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?

Gives concrete polling guidance: pass after_id (latest_id from your previous read) to get only newer messages. The read-vs-post split against lobby_post is implied by the wording but never stated as an explicit 'use X when, use Y when' rule.

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