telegram_scheduled

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

Beyond the readOnly/idempotent annotations, it discloses the ordering (soonest first), the return semantics (due time per message, or an online-delivery flag), the scope limitation (one chat at a time, no global list), and out-of-scope operations (no cancel or early send). This is genuinely additive context, not a restatement of annotations.

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?

Front-loaded with what the tool returns, then routing, then constraints. Sentences are short and each carries information, though the closing note about cancelling/early-send is marginally beyond selection needs.

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 output schema, the description correctly takes on the burden of describing return values (due time per message or online-delivery flag) and does so clearly, alongside the one-chat scoping constraint an agent must honor.

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 100%, so chat, limit, and account are already documented in the schema; the description adds no syntax or format detail for them. Baseline 3 applies when the schema carries the parameter burden.

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 resource and scope: the chat's scheduled queue, ordered soonest first, with due times or an online-delivery flag. It explicitly names the siblings it is not (telegram_drafts, telegram_plan_schedule_message), so an agent can distinguish it without opening any schema.

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?

Gives an explicit use condition ('when the user asks what is queued to send later in one chat'), an explicit exclusion ('Do not use this for unsent drafts'), and names the correct alternatives for both the excluded read and the related write.

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