telemost_stats_reach

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

Annotations already cover readOnly, idempotent, and non-destructive traits. The description adds key behavioral context: the tool is 'Paid per call in USDC from your wallet' and references telemost_catalog for the price, which is crucial for an agent to know before invoking. It also clarifies the resource scope (a channel).

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, front-loaded with the core purpose ('Telegram reach analytics'). The second sentence adds a necessary cost warning and cross-reference to telemost_catalog. No redundant or filler content.

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 simple two-parameter tool with no output schema, the description conveys the tool's purpose, target metric, and cost model. However, it does not explain the aggregation parameter's meaning or return format, which would make it more complete. Overall, it is fairly complete for an agent to decide on 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 coverage is 0%, so the description must compensate. It mentions 'for a channel' which gives some context to the required 'channel' parameter, but it omits any explanation of the 'aggregation' parameter (day/week/month/year). The description adds little meaning beyond the schema for aggregation and does not specify input formats or examples.

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's function: 'average post reach chart for a channel' with a specific metric (reach) and resource (channel). It distinguishes from siblings like telemost_stats_engagement and telemost_stats_subscribers by focusing on 'reach' specifically.

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 description implies usage for analyzing post reach over time but does not explicitly state when to use this tool versus alternatives. It mentions the paid nature and directs to telemost_catalog for pricing, giving an operational guideline, but lacks explicit when-to-use or when-not-to-use guidance.

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