ads_telegram_action_queue_create

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

With no annotations, the description carries the full burden and covers the essentials: mandatory confirm, local-only (no execution), no recipient lookup, and randomized per-action pauses with a default 15–66s window. It omits what happens after creation (persistence, queue identity for later process/cancel), so it is strong but not complete.

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?

Five tight sentences, front-loaded with purpose before constraints and delay behavior. Every clause conveys operative information; no filler or restated title.

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 50-item-batch mutation tool with no output schema and no annotations, the description should say what the caller gets back (queue identifier/status) so it can chain to process/cancel. That linkage is missing, keeping it at adequate rather than complete.

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 60%, and the description fills meaningful gaps: it states the confirm requirement, the default delay range 15–66s that the schema fields only partially imply, and the four supported action shapes (message, chat reply, channel-post reply, reaction). Only project_id goes unmentioned in both description and schema.

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?

Names a specific verb and resource (create an ordered local Telegram action queue) and immediately scopes it: 'from explicitly supplied targets and exact texts' plus 'it does not execute anything.' That cleanly separates it from the process/list/cancel siblings and from direct-send tools like ads_telegram_account_send.

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?

'Requires confirm=true' and 'does not execute anything' tell the agent this is a staging step and that processing is elsewhere. It also rules out discovery ('No recipient discovery is performed'), so an agent knows to supply targets itself. It never names the sibling that runs the queue, which keeps it short of a 5.

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