Get Paginated Messages from Chat

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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description's job is lighter. It adds pagination behavior context ('paginated', 'sequential message retrieval'). Minor imprecision: it says 'offset or limit' while the schema actually uses page/page_size, which is a slight terminology mismatch but not a contradiction.

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 with zero waste: the action, the usage context, and the sibling alternative. The most decision-relevant information (what it does and when to use it) is front-loaded before the alternative routing.

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, rich annotations, and 100% schema param coverage, the description covers what remains: pagination intent and differentiation from search_messages. The only gap is the 'offset or limit' phrasing that doesn't match the page/page_size schema, which could mildly confuse an agent selecting pagination parameters.

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 the schema fully documents all four parameters (page, page_size, account, chat_id). The description adds no real parameter semantics beyond the schema — 'offset or limit' loosely maps to page/page_size but is arguably a slightly less accurate framing. Baseline 3 is appropriate.

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 clearly differentiates from search_messages by naming it explicitly. The title reinforces the same purpose. An agent can immediately tell this tool fetches messages sequentially rather than searching them.

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 explicit when-to-use guidance ('Use for sequential message retrieval') and names the alternative tool with the condition that selects it ('To search text across messages, use search_messages'). Nothing about selection 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.