ads_telegram_ai_trend_snapshot_list

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the operation is read-only and never contacts Telegram, which matters given the telegram-prefixed siblings, but it omits pagination behavior, defaults, sort order, and what a 'snapshot' contains.

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?

One compact sentence with the key scope and safety note front-loaded. It earns its place, though it is so terse that it leaves important semantics unstated.

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 six-parameter list tool with no annotations and no output schema, the description is too thin. An agent still cannot tell what fields a snapshot returns, how limit is applied, what the default project scope means, or how period_start/source_scope constrain results.

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 compensate for six undocumented parameters. It only mentions topic and intent filtering and says nothing about limit, project_id (which has a default of 'neron'), period_start, or source_scope.

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 ('List saved weekly demand snapshots') and scopes it by topic and intent. It implicitly distinguishes itself from the sibling build tool by emphasizing 'saved' snapshots, but never names the build alternative explicitly.

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 weekly demand snapshots' and 'read-only and never contacts Telegram' imply this is for browsing stored trend data rather than live Telegram collection. However, it does not explicitly say when to use this versus ads_telegram_ai_trend_snapshot_build or other telegram_ai search/query list tools.

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