Get Paginated Messages from Chat

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds only that results are sequential/paginated, which the schema also conveys; it says nothing about ordering, rate limits, or multi-account fan-out behavior (that detail lives only in the schema).

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 tight sentences, front-loaded with purpose before the routing guidance, with no padding. The only blemish is the mildly misleading 'offset or limit' clause, which costs it a perfect score.

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 a full output schema, complete parameter descriptions and rich annotations, the description only needs to cover purpose and tool selection, which it does. Ordering semantics and multi-account behavior are left implicit, but those are adequately covered elsewhere.

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 page, page_size, account and chat_id are all well documented in structured data; baseline is 3. The description contributes no additional parameter meaning and its 'offset or limit' phrasing does not match the actual page-based parameters.

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 ('retrieve paginated messages from a specific chat') and distinguishes itself from siblings by naming list_messages and search_messages. The phrase 'starting from an offset or limit' is slightly imprecise since the schema actually exposes page/page_size, not offset/limit, which mildly blurs what the tool does.

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?

Explicitly states the selection condition ('Use for sequential message retrieval') and routes the agent to the correct alternative for two distinct cases: filtering by sender/date goes to list_messages, text search goes to search_messages. Nothing is left to inference.

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