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

Annotations fully cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is low, but the description adds essentially nothing beyond metric names that already appear in the body text. No mention of scope, freshness, or what the summary aggregates over.

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?

One line plus a bilingual restatement — very lean, arguably under-specified rather than wasteful. The metric list is truncated with an ellipsis, which costs information without saving much space.

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?

For a zero-arg summary tool with a rich sibling set (members_north_star, members_cross_platform, acquisition_stats), the description is too thin to route or interpret results. No output shape is hinted at and no scope boundary is given.

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?

Zero parameters, so the baseline is 4. There are no argument semantics to explain and none are invented, which is the right call.

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?

States a resource and deliverable type (totals/summary) with named example metrics, but is mostly a restatement of the tool name. It does not distinguish itself from siblings like members_north_star, members_cross_platform, or acquisition_stats, which an agent would need to route correctly.

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?

There is no statement of when to use this rather than the adjacent members_* or *_stats tools. The agent is left to infer the scope (all members? platform-wide? current or historical?) with no exclusions or alternatives named.

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