telegram-get-megagroup-stats

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

Annotations (readOnlyHint, openWorldHint) already indicate safe read with dynamic schema. Beyond that, description adds admin rights requirement and specific rate limiting details, which are critical for agent planning and not covered by 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?

Three sentences pack essential details: data contents, sibling differentiation + prerequisite, and rate limit warning. No extraneous text, information is front-loaded.

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?

Despite no output schema, description covers return value types (members, messages, viewers, etc.) and explains the effect of includeGraphs. Together with annotations and guidance, the agent has sufficient context to use the tool correctly.

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 100% with adequate descriptions for all 3 parameters. The description does not add much more about parameters themselves but provides context about the return data (current vs previous period, top lists). Baseline 3 is appropriate as schema carries the load.

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 verb 'Get', the resource 'supergroup statistics', and enumerates specific data types (members, messages, viewers, posters, top lists). It also distinguishes from the sibling tool for broadcast channels, making purpose unambiguous.

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?

Provides explicit when-to-use (supergroups only), when-not-to-use (use telegram-get-broadcast-stats for broadcasts), prerequisites (admin rights), and behavior (rate limit of ~1/30 min with expected FLOOD_WAIT). This fully guides agent decision-making.

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