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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds useful content detail (what dimensions are counted, that it surfaces 'new to Pulse' projects) but says nothing about data freshness, caching, or aggregation window boundaries.

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 front-loaded sentence that enumerates the returned dimensions efficiently with no filler. Slightly dense as a comma-list, but every clause identifies a distinct output facet.

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 one optional parameter, no output schema, and annotations covering the safety profile, the description does its main remaining job well: telling the agent what the response will contain. Only minor gaps (freshness, whether counts are cumulative vs daily) remain.

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% and the enum is documented, so the schema carries the load. The description restates the period options but adds no semantics beyond them (e.g., how 'day' is defined or the default), so 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?

States a specific resource and scope: aggregate CKB ecosystem stats over day/week/month, including counts, most active entities, and new projects. This is clearly distinguishable from the entity-specific siblings (person, project, find_projects), though it never names them explicitly.

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 is only implied – an agent can infer this is the 'summary/dashboard' entry point versus the targeted lookups in the sibling set, but the description never says when to choose it over recent_updates or trends, nor any prerequisite.

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