get_analytics_group_users

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds context about pagination, per-user breakdown structure, and enterprise gating. It does not contradict annotations. No rate limit or permission details beyond the enterprise gate, but the rich annotations cover the main traits.

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?

Two sentences, no wasted words. First sentence front-loads the core purpose and data shape. Second sentence provides usage guidance and restrictions. Highly efficient.

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?

Given the high schema coverage and existence of output schema, the description is complete. It covers purpose, usage, restrictions, basic data structure, and distinguishes from a sibling. The pagination mention aligns with the schema parameters. No missing critical context.

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%, so the baseline is 3. The description does not add parameter-specific meaning beyond what the schema already provides. It mentions 'paginated' implicitly but no parameter details are needed given the complete 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 clearly states it retrieves a paginated per-user breakdown with specific fields (total_groups, group_count, users array with request count, cost, token usage). It distinguishes from sibling get_users_analytics by naming the alternative and its purpose.

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?

Explicitly states when to use: 'for billing, audits, or top-consumer analysis'. Directs to an alternative tool for aggregate trends. Also discloses the enterprise-gating restriction and the 403 error on non-Enterprise plans.

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