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

With no annotations, the description carries the disclosure burden. It explicitly states the required permission (read:analytics), the trailing-window behavior with default 30, and the exact set of metrics included, and clarifies that definitions match the admin dashboard. It could go further on response shape or pagination, but for a read-only summary tool this is strong.

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 description is a single dense sentence that front-loads the purpose and window, then lists metric categories, dashboard alignment, and permission. Every clause adds useful information and there is no filler.

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 simple one-parameter read tool, the description covers the window, default, permission, and metric contents well enough to invoke it correctly. There is no output schema, and the description does not explicitly describe the response envelope, but the enumerated metric list gives a clear picture of what the summary includes.

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% for the single parameter, and the schema already documents days as a 1-365 trailing window with a default of 30. The description restates the default and trailing-window concept but adds no new parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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 a specific resource (community analytics) and a specific action (get summary over a trailing window), then enumerates the included metrics. This is enough to distinguish it from siblings like hivelearn_get_course_analytics and hivelearn_get_leaderboard without needing the schema.

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?

No explicit guidance about when to choose this tool over alternatives. It notes the default time window and the read:analytics permission requirement, but does not say when to prefer this over course analytics, leaderboards, or other analytics-oriented sibling tools.

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