ads_telegram_ai_search_query_list

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

With no annotations, the description carries full behavioral burden; it usefully discloses read-only semantics and that it never contacts Telegram (a meaningful reassurance for a Telegram-labeled tool). However, it omits return shape, pagination/ordering behavior, and what the counters represent, leaving real gaps for a no-annotation tool.

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 tight sentence that front-loads the resource and the key constraint (read-only, no Telegram contact). No wasted words, though the semicolon clause could be split for scannability.

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 no annotations, no output schema, and four undocumented parameters, the description leaves too much for the agent to infer – especially the meaning of topic/status filters and the counters returned. Given the tool's parameterized filter surface, it should explain at least the scoping and filtering behavior.

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?

The schema has 4 parameters at 0% description coverage, and the description explains none of them – it says nothing about limit, topic, status enum values, or project_id scoping. The reference to 'counters' does not map to any parameter, so the coverage gap is unaddressed.

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 (list) and resource (saved Telegram AI search phrases) plus the extra data returned (last-run/result counters). It is distinguishable from ads_telegram_ai_search_query_upsert and ads_telegram_ai_search_run_list by being a read of saved phrases rather than runs, though it never names a sibling to make the split explicit.

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?

The phrase 'saved ... phrases' implies this retrieves stored queries rather than executing or creating them, giving some usage context. But there is no explicit when-to-use guidance, no mention of when to prefer ads_telegram_ai_search_run_list, and no stated prerequisites or exclusions.

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