ads_telegram_channel_direct_check

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

With no annotations, the description carries the full burden and discloses key behavior: read-only operation, no joining/sending/posting, and the Premium requirement. It does not cover rate limits or authentication details beyond Premium, but the safety profile is clear.

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?

A single front-loaded sentence with a colon-separated list. Every clause adds information: purpose, what is checked, prerequisite, and safety guarantees.

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 one-parameter read-only tool with no output schema, the description explains what is checked and the key constraints. It does not describe the return format, but the core operational and safety context is sufficient for invocation.

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%, and the single 'channel' parameter is already documented as '@username or t.me public channel'. The description adds no further meaning about the parameter, so the baseline of 3 is appropriate.

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 and resource: a read-only preflight that checks DMs, the connected discussion chat, and public contacts for a broadcast Telegram channel. It clearly distinguishes itself from the sibling send tool by emphasizing that it never joins, sends, or creates a public post.

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?

The term 'preflight' implies use before broadcasting, and 'Requires Telegram Premium' gives an important prerequisite. However, it does not explicitly name when to use this versus ads_telegram_channel_direct_send or state exclusions beyond the side-effect guarantees.

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