Productivity summary

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that this is a rollup combining Overall3, stats, and Analytics metrics, but it does not disclose aggregation behavior or the effect of the raw flag.

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 sentence with no filler, and the core purpose is front-loaded. 'Overall3 + stats + Analytics metrics' is compact and substantive, even if the term Overall3 is somewhat cryptic.

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 an output schema present and readOnly annotations available, the description does not need to explain return values or safety. However, the meaning of 'Overall3' and the raw/period behavior remain under-explained, and the description does little to help an agent choose this over closely related summary tools.

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?

The schema already documents most parameters with 83% coverage, including period, user_id, group_id, and date ranges. The description adds little parameter-level meaning beyond reinforcing the per-user nature, which is already present in the user_id parameter.

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 clear resource and action: it returns a per-user productivity rollup and names the metric components (Overall3, stats, Analytics metrics). It is distinguishable from idle/activity summaries at a glance, though it does not explicitly contrast with siblings.

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 is given for when to use this tool versus alternatives like get_activity_summary, get_idle_summary, or get_analytics. The sibling list is provided but the description does not route the agent toward or away from any alternative.

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