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

Beyond readOnly/idempotent annotations, the description discloses plan gating, the exact plan_limit failure mode with upgradeUrl/stillWorks/alternatives, the solo-team state, and that names/emails/document text are untrusted. These are meaningful operational and safety details that an agent would not get from annotations alone.

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?

The opening clause is front-loaded and useful, but the body is a dense wall of semicolon-separated definitions that is hard to scan. Much of the detail is valuable because there is no output schema, but the structure could be clearer and more segmented.

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?

With no output schema, the description carries the return-shape burden and does so thoroughly: per-member fields, totals behavior, distinct-reader caveat, series, state values, and failure behavior are all explained. An agent has enough information to call the tool and interpret its output 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%, so the schema already fully documents range and includeMemberSeries, including defaults and enum values. The description adds only minor context about range matching Metrics page ranges and does not explain includeMemberSeries, so the baseline 3 is appropriate.

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 states exactly what the tool returns: per-member activity over a selected range, corresponding to the Team tab of the Metrics page. It distinguishes the resource from sibling stats tools by emphasizing one row per owner/admin/member and explaining that agent work rolls up to the member.

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 clear: choose a 7d/30d/90d range, defaulting to 30d, and note that the tool is for team-level metrics. It also explains the Pro-only requirement and points to lnkdrp_whoami for capability checks, though it does not explicitly compare this tool with lnkdrp_get_project_stats or lnkdrp_get_share_stats.

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