get_stats

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

The description adds the admin constraint, which is not already present in the annotations. Since annotations already declare read-only, idempotent, and non-destructive behavior, this additional context is useful. It doesn't contradict the 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?

The description is a single, efficient sentence that front-loads the core purpose and the admin constraint. Every word contributes value, with 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?

With an output schema present and annotations covering safety, the description provides the essential purpose. However, it lacks parameter semantics and sibling differentiation, leaving notable gaps for a simple tool that could have been fully specified.

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 0%, so the description must compensate. It doesn't explain the `chat` parameter's format (e.g., username vs. numeric ID), though the name and context imply it's the channel/supergroup identifier. This is minimal guidance at best.

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 retrieves statistics for a channel or supergroup, using a specific verb and resource. It narrows the scope but doesn't explicitly distinguish from sibling tools like `dialog_stats`.

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 mentions the admin requirement, providing a clear context for when this tool should be used. However, it doesn't offer guidance on choosing between this and similar stats-related tools, nor does it state any exclusions.

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