telegram-get-broadcast-stats

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, which the description does not contradict. The description adds behavioral context about required permissions (admin rights, Premium). It does not fully describe failure cases or data freshness, but it is transparent about key requirements.

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 sentences, no fluff. The first sentence states the core function and data, the second provides constraints and alternatives. Every word earns its place.

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?

Given no output schema, the description lists the types of data returned (followers, views, etc.), which is helpful. It hints at includeGraphs for raw data. It could be more complete by describing the output structure, but it is adequate for a stats tool with sibling differentiation.

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 100% with decent parameter descriptions. The description adds context about includeGraphs returning raw graph data and chatId being for broadcast channels, but this is marginal beyond the schema. Baseline 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?

The description clearly states it gets broadcast channel statistics and lists specific metrics (followers, views, shares, reactions). It distinguishes itself from the sibling tool 'telegram-get-megagroup-stats' for supergroups, making the purpose unambiguous.

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 explicitly says when to use (broadcast channels only) and when not to (supergroups should use telegram-get-megagroup-stats). It also notes admin rights and potential Premium requirement, providing clear usage context.

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