start_broadcast

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

The description warns that it sends real Telegram messages to many users, implying side effects. However, with no annotations, more detail on auth needs, rate limits, or irreversible consequences would improve transparency.

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?

Two concise sentences, one conveying purpose and one warning, with no redundant information. Efficient and appropriate length.

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?

Lacks mention of return value (e.g., broadcast ID) and permissions, given no output schema. Adequate for basic understanding but incomplete for a complex tool with side effects.

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 high (80%), so the baseline is 3. The description mentions 'matching the given filters' but adds no extra meaning beyond schema definitions for filters, body, or confirm.

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 clearly states the tool starts a broadcast job sending a message to matching subscribers, using specific verbs and resource. It distinguishes from siblings like stop_broadcast and modify_broadcast.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., modify_broadcast, stop_broadcast). The warning 'use with caution' hints at careful use but doesn't set prerequisites or exclusions.

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