Get Full Message History from Chat

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so "Read-only operation" merely repeats structured data. The description adds the ordering guarantee ("chronological") and limit-bounded behavior, which is mild extra context but no statement of return shape, pagination, or behavior on a missing/unresolvable chat.

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 the core action and scope, with no filler. Slightly terse for a tool in such a crowded namespace, but nothing is wasted.

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 so return values needn't be explained, and annotations carry the safety profile. The description covers purpose, use case, and limit scoping adequately; the main omission is any differentiation from the many similar message-retrieval siblings.

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 already documents limit, account, and chat_id semantics thoroughly. The description only echoes the limit cap ("up to the configured limit") and adds nothing about ordering, defaults, or multi-account fan-out beyond what the schema states; baseline 3 applies.

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?

The description states a specific verb and resource (retrieve complete chronological message history from a chat) with scope (up to the configured limit). However, it makes no attempt to distinguish itself from near-duplicate siblings such as get_messages, list_messages, and get_full_chat, leaving the agent to guess which history-retrieval tool to pick.

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?

"Use when ingesting or summarizing a conversation" provides a genuine use context, but there are no exclusions and no reference to the many sibling tools (get_messages, list_messages, search_messages) that appear to overlap heavily. When-to-use is implied rather than fully clarified.

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