get_kb_stats

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the VG-only applicability constraint, which is genuinely useful, but says nothing about what the 'statistics' consist of, despite there being no output schema.

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?

One front-loaded sentence with zero waste. It is arguably too terse for a tool with no output schema, but nothing is redundant or buried.

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 output schema, the description is the only place a caller could learn what the returned statistics contain, and it does not say. The VG-only qualifier is a real and necessary addition, but the return shape remains opaque for a read tool whose siblings overlap.

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?

There is a single required parameter with 100% schema description coverage ('The agent ID'), so the schema carries the parameter semantics. The description adds only the implicit note that the agent must be a VG agent, not any id format or lookup guidance.

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 verb and resource (get knowledge base statistics) plus the scope (for an agent) and a platform restriction (VG agents only). An agent can grasp the purpose immediately, though it does not distinguish this from the nearby get_kb_quota sibling, which covers similar ground.

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?

The only guidance is the parenthetical '(VG agents only)' restriction. There is no statement of when to prefer this over get_kb_quota or get_kb_docs_bulk, nor any prerequisite, rate-limit, or failure context beyond the platform qualifier.

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