ads_telegram_public_post_reply

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

With no annotations, the description carries the behavioral burden well: it discloses the Premium requirement, explicit confirmation, a read-only preflight that does not block the write, and important restrictions around private messaging, moderation, and guest-send. It does not cover error behavior or return details, but it provides substantial safety and permission context for a mutation tool.

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?

The description is dense but front-loaded, placing the core action and conditions before secondary caveats. It avoids wasted sentences, though the single long sentence packs multiple constraints together and could be slightly easier to parse.

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 public-posting mutation tool with no annotations and no output schema, the description covers prerequisites, safety constraints, and preflight behavior well. However, it leaves key parameters such as message_id and text unexplained, so it is not fully complete for an agent invoking the tool.

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 50%, and the description adds little parameter meaning beyond mentioning confirm=true and Telegram Premium. It does not explain message_id, the required reply text, or constraints such as text length, leaving half the parameters undocumented in both schema and description.

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 precise verb and resource: 'Reply publicly to one Telegram channel post through its linked discussion.' It also differentiates the operation from private messaging by explicitly saying it 'never sends a private message,' which helps separate it from siblings like ads_telegram_chat_reply or 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?

It gives clear conditions for use: only when the post contains a relevant explicit request and resource rules permit it, plus the prerequisites of Telegram Premium and confirm=true. It also states what the tool will not do, but it does not explicitly name alternative tools for adjacent cases.

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