Bot: new messages

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

The description says the call will 'mark them read', which mutates server-side read state, yet the annotations declare readOnlyHint=true (and idempotentHint=true). This directly contradicts the annotation: a get-that-writes is not a read-only tool. Aside from that, the description does add genuinely useful context (failure mode when a webhook is set, message shape, prompt-injection warning), but the contradiction is disqualifying.

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 purpose and side effect in the first sentence, then message shape, then a security note, then the failure condition. Every sentence carries information an agent needs; no filler.

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 an output schema present and 100% schema coverage, the description is nearly complete: it covers purpose, scope, message structure, alternatives, failure mode and injection risk. The one gap is that the mutation implied by 'mark them read' is not reconciled with the read-only annotation.

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?

There is a single optional parameter (limit) and schema coverage is 100%, so the schema already carries the meaning, bounds and default. The description adds no parameter detail, so the baseline 3 for fully-documented parameters is correct.

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 (get messages sent to the bot) plus the scope (since last check, all chats, oldest first). An agent can immediately distinguish this from siblings like bot_search_messages, bot_read_chat and bot_wait_for_reply.

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 clear context for use and names two sibling alternatives with the condition that selects them (bot_download_file for media, bot_get_webhook_info when a webhook is set). It does not explicitly contrast against bot_search_messages or bot_wait_for_reply, so routing is good but not exhaustive.

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