ads_telegram_action_queue_process

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

With no annotations, the description carries the full disclosure burden and does substantial work: sequential execution, Premium gating, confirm=true, interval waiting, no retries, and stop-on-first-error. It still leaves the post-failure state ambiguous — whether unprocessed actions remain queued, are marked failed, or must be cancelled via ads_telegram_action_queue_cancel.

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 dense sentence with the action, its preconditions, and its execution semantics front-loaded. No filler; every clause conveys a distinct behavioral fact.

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 destructive, confirmation-gated execution tool with no output schema, the description covers gating, sequencing, pacing, and failure behavior — enough to call it safely. The remaining gap is return/partial-failure reporting and the max_actions semantics, which an agent would need to reason about batching.

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 75% and the description's 'confirm=true' and 'waits at least the configured interval' loosely align with the confirm and wait_for_interval parameters. It adds nothing about the significant max_actions parameter (defaults to 1, caps at 50), which governs how much of the queue is consumed per run.

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 ('Execute') and resource ('Telegram action queue') with an explicit scope qualifier ('explicitly approved ... in sequence'). Clearly distinguishable from siblings ads_telegram_action_queue_list/cancel/create, which handle other lifecycle stages.

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?

Establishes prerequisites well: the queue must be 'explicitly approved', Premium is required, and confirm=true is mandatory. It does not name an alternative tool or say what to do when the queue is not approved (e.g., direct the agent to ads_telegram_action_queue_create or the individual send tools), so routing guidance is clear but not exhaustive.

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