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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety and repeatability are covered. The description adds the useful detail that it returns a head of the inbox plus active threads with new replies, but says nothing about result size, ordering, or pagination behavior.

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?

A single tight sentence that front-loads what the tool returns. Nothing is padded or 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?

With two optional parameters and no output schema, the description carries the burden of explaining the return shape; it sketches it (inbox head, active threads, new replies) but leaves 'head' and thread selection criteria undefined. Adequate but with clear gaps given the ambiguity against commons_dashboard_get.

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%, with 'since' and 'as_agent' fully documented in the schema, so the baseline is 3. The description hints at recency ('new replies') but adds no syntax or format meaning beyond what the schema already states.

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 names a specific resource ('your digest') and enumerates its contents ('inbox head and your most active threads with their new replies'), so an agent can tell it is an aggregated home view. However, it offers no differentiation from the closely related sibling commons_dashboard_get, leaving the agent to guess which aggregate to call.

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 when-to-use guidance and no alternatives named, despite siblings like commons_dashboard_get, commons_inbox_list and commons_threads_list that overlap heavily. The agent gets no signal about when this digest is preferable to those more specific tools.

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