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

Beyond readOnlyHint=true, the description discloses important behavioral details: 30d/all silently fall back to 7d for free groups, range.key should be checked, verbatim member messages are never included, and private groups have member identities, description, and member_count withheld. This gives the agent realistic expectations about output and limitations.

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?

Every sentence carries selection, parameter, behavior, or privacy information. The trigger is front-loaded, followed by slug, return contents, range caveat, and privacy constraints. The output enumeration is dense but useful 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 definition covers selection, parameter semantics, return shape, paid-plan fallback, and privacy handling, which is more than enough for reliable invocation. It does not mention error behavior for invalid or nonexistent slugs, but the detailed schema and output description make that a minor omission.

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%, so the schema already documents slug and range. The description adds value by explaining the slug URL pattern and, more importantly, by telling the agent to verify range.key because wider ranges may silently fall back. That operational guidance goes beyond the schema.

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 opens with 'Call this when the user asks about the activity, health, leaderboard, mood, or trends of a specific Telegram group tracked by Limzo', naming the exact resource and scope. It is clearly distinguishable from get_global_stats and list_groups because it emphasizes a single Telegram group and its 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 gives explicit trigger conditions ('Call this when...') and a precise scope, so an agent knows when this tool is appropriate. It does not explicitly name the sibling alternatives or state when to choose them, but the 'specific Telegram group' scoping is strong enough to avoid obvious confusion.

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