Get group stats

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

Beyond the readOnly/idempotent annotations, it discloses a real latency profile ('up to about 15 seconds' because computation is backgrounded) and the exact failure mode for non-admins (APP_PERMISSION_DENIED). It also explains how each metric is derived, which tells the agent these numbers are dashboard-sourced and may not match a manual count.

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?

Front-loaded with the payload and the admin gate, followed by metric definitions and latency. Nearly every sentence carries new information, though 'Admins only' is stated twice and could be consolidated.

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?

There is no output schema, yet the description itemizes the returned fields and their units (MRR in US dollars), states the period semantics, the latency, and the auth failure. Nothing material is missing for an agent to call this 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 already 100%, so baseline would be 3, but the description adds genuine meaning: it defines what 7d/30d mean (growth of the daily member count) versus 90d (sum of three months of the members chart). The `group` parameter adds nothing beyond the schema, keeping it from a 5.

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 first sentence names the exact metrics returned (total/new/churned members plus MRR) and the period scope, which is far more specific than the title's 'Get group stats'. It doesn't distinguish itself from nearby siblings like get_group or get_leaderboard, but the resource and output are 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?

Usage context is implied: it returns dashboard analytics for a group you administer, and the admin restriction is stated. However, with ~70 siblings including get_group, get_leaderboard and search_members, the description never says when to prefer this tool over those, so the agent must infer the boundary.

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