refresh_stats

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

Adds 'global' scope and clarifies that the destructive operation performs a recalculation (not deletion), complementing the destructive=true annotation without contradiction.

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?

Single front-loaded sentence where every word ('Force', 'global', 'recalculation') earns its place; no redundancy.

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?

Adequate for a parameterless tool; covers action, scope, and domain sufficiently given the lack of output schema.

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?

Zero-parameter tool triggers baseline score of 4; schema requires no additional semantic elaboration.

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?

Clear specific action (force recalculation) and target (global telegram-archive statistics), implicitly distinguishing from sibling get_chat_stats by emphasizing 'recalculation' vs 'get'.

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 word 'Force' implies usage when fresh data is needed, but lacks explicit when-to-use guidance or contrast with retrieval alternatives.

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