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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description is not burdened with the safety profile. It adds real context beyond them: an admin-only permission gate and the requirement for a Cotlet API key with access to the app. It could say more about the data lag or freshness relative to the dashboard, but the access requirements are genuinely useful.

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 sentence is padded with near-verbatim repetition: the metric list appears twice ('total, new and churned members and monthly recurring revenue' then 'total members, new joins, churned members and monthly recurring revenue') and 'Admins only' is stated twice. The core fact is front-loaded, but two of five sentences are redundant.

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, so the description must carry the return-value burden, and it does enumerate the returned figures (membership and revenue numbers matching the admin dashboard). Access constraints are also covered. Only minor gaps remain, such as comparability across periods or data timing.

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%, including the period enum values with a documented default, so the schema does the heavy lifting. The description only restates 'for a period' and the metric set without adding format or syntax detail beyond the schema, making baseline 3 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 a specific verb and resource with concrete metrics: total members, new joins, churned members and monthly recurring revenue. It is immediately clear what the tool returns and how it differs in kind from list-style siblings like skool_list_members. It stops short of naming a sibling or contrasting scope, so it is clear but not sibling-differentiating.

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 by 'Admins only' and 'for a period', telling the agent this is an admin-facing aggregate report. However, there is no explicit when-to-use, when-not-to-use, or which sibling to pick for member-level detail versus aggregate stats, so the agent must infer routing.

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