get_chat_stats

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

readOnlyHint=true already tells the agent this is a safe read, so the description carries a lower burden. But it adds nothing about what 'statistics' contains, whether results are cached, or how it relates to refresh_stats — meaningful gaps for a stats-retrieval tool whose sibling implies staleness control.

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?

A single efficient sentence with the resource front-loaded. No waste, though also no additional structure to aid scanning.

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?

With no output schema and no annotations beyond readOnlyHint, the description should explain what statistics are returned or at least the freshness model. Given the sibling refresh_stats exists, the omission of any staleness/caching semantics leaves the agent unable to choose confidently between the two.

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 100% for the single chat_id parameter, so the schema fully documents the input. The description adds no format hints (e.g., numeric vs. @username) beyond the schema, which is the expected baseline.

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?

States a specific verb (Get) and resource (statistics) scoped to a Telegram chat, so the action is unambiguous. It does not, however, distinguish itself from the sibling refresh_stats, which an agent must reason about when deciding whether stats are stale.

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 guidance on when to call this versus refresh_stats, or whether it returns cached vs. freshly computed statistics. The agent is left to infer usage entirely from the name.

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