ads_telegram_ai_trend_snapshot_build

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

With no annotations, the description usefully discloses the side-effect scope: it changes only local analytics tables and never contacts Telegram. It still omits other important behavior for a mutating build tool, such as whether builds are idempotent, what reset does, required permissions, or expected output.

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?

Two tightly written sentences, front-loaded with the main action and followed by the key safety constraint. Nothing is repetitive or 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?

The description gives enough context to understand the core operation and its local-only effect. However, for a four-parameter mutating tool with no annotations, no output schema, and only half the parameters described in schema, it should cover more about parameter usage and build 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?

Schema description coverage is only 50%, and the description adds no meaning for specific parameters. It does not explain source_scope enum values, project_id behavior, or when reset should be used, leaving the agent to rely on incomplete schema prose.

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 verb ('Build') and resource ('weekly demand snapshot'), and adds grouping dimensions ('topic and intent') plus deduplicated source counts. It is clearly a build/write operation rather than a listing operation, but it does not explicitly differentiate itself from the sibling list tool.

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?

Usage is implied by the purpose: build a weekly demand snapshot for local analytics. However, the description does not say when to use this instead of ads_telegram_ai_trend_snapshot_list or related research-stat tools, nor does it mention preconditions or exclusions.

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