kernel_marketplace_stats

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

No annotations exist, so the description carries the full behavioral burden, yet it only enumerates return categories. It does not state whether the stats are global or account-scoped, whether they are cached/live, whether any permission is needed, or how large the payload is — all things an agent needs for a zero-parameter, zero-annotation tool.

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 with no filler, and the key noun 'marketplace statistics' appears first. It is arguably too terse on what 'install stats' and 'ratings' concretely contain, but nothing is wasted.

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 no parameters, no annotations, and no output schema, the description is the only source of information about the return value, and it gives categories but not shape or scope. Adequate for a simple read-only aggregate call, but it leaves real questions open.

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 tool takes no parameters, so there is nothing for the description to disambiguate about inputs; the baseline of 4 applies. The description instead spends its words on output categories, which is the sensible use of space here.

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?

Clear verb+resource ('Get marketplace statistics') followed by the specific metric families returned: item counts by type, install stats, ratings. An agent can distinguish it from sibling listing tools like kernel_marketplace_browse or kernel_marketplace_get, though the description never names those alternatives 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 by the word 'statistics' — an agent can infer this is for aggregate numbers rather than item-level browsing or install actions. There is no explicit statement of when to prefer this over kernel_marketplace_browse or kernel_marketplace_get.

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