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

With annotations already declaring read-only, idempotent, non-destructive behavior, the description adds useful context: watches originate from the panel and the tool returns the key fields of each watch. It does not cover pagination, authorization needs, or behavior when account filters are omitted, but it meaningfully extends beyond what annotations provide.

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?

The description is two compact sentences with the read-only marker and core resource definition front-loaded. The parenthetical field list and account mapping are dense but all directly useful for invoking and interpreting the 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?

For a simple read-only list tool with no output schema, the description is quite complete: it identifies the resource, lists returned fields, and explains the read-only/mutation boundary plus account parameter mapping. The main gaps are what happens when neither account identifier is provided and whether both can be supplied together.

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%, so the description must carry parameter meaning. It explains that account_id maps to tg_account_id and that account_uuid can be passed instead, substantially compensating for the missing schema descriptions, though it does not clarify whether both may be supplied or what happens if neither is provided.

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 read/list operation for Telegram keyword watches and enumerates what the records represent and contain, including chat, keywords, mode, status, and match metadata. It also clarifies the mutation boundary by saying watches are set up in the panel and cannot be created or changed here, making the resource scope clear.

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?

It gives clear usage context by explaining that watches are managed in the panel and cannot be created or changed via this tool, which steers mutation attempts away. It does not explicitly name alternatives such as list_tg_matches for match records, so sibling routing is only partially covered.

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