telemost_stats_words

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

Beyond the read-only/idempotent annotations, the description discloses billing behavior ('Paid per call in USDC from your wallet') and the time constraint ('searches posts from the last 14 days'). This adds meaningful operational context not present in annotations.

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 deliver purpose, modes, use case, time window, and cost. No filler or redundancy; information is front-loaded and each clause 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?

The description covers purpose, modes, use case, time window, and cost, but does not explain all parameters nor describe the return value (no output schema). Given the tool's moderate complexity and missing param semantics, it is adequate but has clear gaps.

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 explains the 'mode' parameter via 'by-period' and 'by-channels' and implies 'word' is the keyword/brand. However, 'period' and 'extended' are not explained at all, leaving half the parameters ambiguous.

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 specific purpose: 'Telegram keyword and brand tracking' with clear modes ('by-period' vs 'by-channels'). It distinguishes this tool from sibling stats tools by focusing on keyword/brand volume rather than engagement, reach, or subscribers.

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 provides clear context: 'Social listening and market research' and notes the 14-day search window. It does not explicitly name alternative tools, but the context implies when this tool is appropriate for tracking specific terms across channels.

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