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

Annotations already declare write, destructive, open-world and non-idempotent, so the safety profile is covered. The description adds real context beyond that: the 5000-chat cap per call, that chats may come from any of the merchant's accounts, and that the response carries the new list's id and uuid. It does not mention failure modes or auth requirements, which keeps it short of a 5.

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 the [write] marker first and the follow-up tool named last; every clause carries information. The nested parentheticals make it denser than necessary 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?

For a 1-required-parameter mutation with no output schema, the description supplies the result shape (id and uuid), the batch limit, and the account-scoping semantics. Only error behavior and title/description constraints are absent, which is acceptable here.

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 coverage is 0%, so the description must carry the load, and it does for the ambiguous parameters: account_id/account_uuid are optional and denote the owning account, tg_chat_ids accepts cross-account chats with a 5000-item ceiling. Only tg_list_title and tg_list_description are left unexplained, and those are self-evident from their names.

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 ("Creates a saved chat list") and scopes it to the merchant, which cleanly separates it from create_tg_campaign and add_tg_list_members. An agent can identify the operation and its output without opening the schema.

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 routes follow-up work to add_tg_list_members and clarifies that account scoping is optional, so the agent knows how to proceed after creation. It lacks an explicit when-not condition (e.g., versus creating a list via a campaign flow) but the context is clear enough to select the tool.

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