chats_sync

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only transport plumbing (REST path, gRPC method, socket event) and says nothing about whether syncing merges, overwrites, or deduplicates existing chats, or how expensive/rate-limited it is.

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?

A single front-loaded sentence with no filler. The parenthetical endpoint/gRPC/socket metadata is arguably noise for an invoking agent but is compact and does not obscure the main clause.

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?

For a mutation-style import with no output schema, the description omits the things an agent most needs: what 'import' does to existing local chats, whether it is idempotent, and what the result contains. Annotations cover only the coarse safety profile, so the definition is under-specified for the operation's risk.

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?

Only one parameter exists and schema description coverage is 0%, so the description must carry the burden. 'For a channel' loosely signals that channelId identifies the target, but it adds no format, validity, or semantics beyond that, leaving the single input essentially undocumented outside of an example value.

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 verb ('Import') and resource ('the platform's chat list for a channel') are specific, so the agent knows this pulls chat data into the local store. It does not, however, distinguish itself from the many adjacent siblings such as chats_list, chats_get, or chats_search, which an agent could easily confuse with it.

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 statement of when to call this rather than chats_list or chats_get, nor any prerequisite (e.g. a loaded/connected channel). The tool name implies a sync/refresh operation but the description never says when syncing is warranted.

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