messages_sync

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

Annotations already supply the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description's phrasing 'Pull a page of a chat's history' reads like a pure fetch, which sits awkwardly with readOnlyHint=false and would mislead an agent about side effects (e.g. whether the sync cursor or server state advances). No pagination behavior, rate limits, or cursor-advance semantics are disclosed. Not an explicit contradiction, but the read/write framing is left ambiguous.

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?

Single sentence, front-loaded with the action and resource, followed by a compact parenthetical of transport identifiers. Nothing is padded, though the transport triple is developer metadata of limited value to an agent choosing a tool.

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 4 undocumented parameters, no output schema, and a sync operation whose mutation semantics are unstated, the description is not complete enough to invoke this tool correctly. It omits what a page contains, how to detect the end of history, and how this differs from the other history-listing 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 0% for all four parameters, so the schema provides only names and examples. The description hints that results are paged ('a page of a chat's history'), which loosely implies limit/cursor, but it never explains cursor semantics, default/max limit, or the roles of chatId vs channelId. This is far short of compensating for the coverage gap.

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 names a specific verb and resource with scope ('Pull a page of a chat's history'), so the agent knows exactly what operation this is. However, it never distinguishes itself from the closely-named siblings messages_history, messages_list, or messages_get, so the agent cannot tell which history-retrieval tool is correct from the definition alone.

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?

There is no when-to-use guidance, no when-not-to-use, and no mention of any alternative among messages_history / messages_list / messages_get. The parenthetical transport metadata (POST path, gRPC method, socket event) documents how the call is routed, not when the agent should choose it.

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