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

With no annotations, the description carries the full behavioral burden and does disclose that the response is aggregate counts with no per-entity or personal detail ('nothing about anyone'), which is useful data-minimization context. However, it omits whether the operation is read-only, whether it requires authentication, and how the counts are grouped, so substantial gaps remain.

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 compact sentence with no filler, and the key idea (recorded volume and external key count) is front-loaded. It is appropriately sized for a zero-parameter tool, though the awkward phrasing slightly reduces clarity rather than wasting words.

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?

There is no output schema, so the description must explain what the returned counts look like, and it does not: it never says whether counts are totals, per-period, or per-key, nor what 'keys that are not ours' means operationally. For a tool whose entire value is the shape of its numeric output, this leaves the agent guessing.

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 zero parameters, so there is no parameter semantics for the description to add. The baseline for a parameterless tool is 4, and the empty schema confirms nothing is missing.

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 gestures at usage counts ('how much is recorded') and a count of external keys ('by how many keys that are not ours'), but it never states a clear verb or resource and reads more like a riddle than a tool definition. An agent can infer it returns aggregate counts, but cannot confidently distinguish its exact scope from siblings like get_ledger_attestation or get_checkpoint.

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, no mention of alternatives, and no exclusions. The only qualifier ('counts only, nothing about anyone') describes output content, not invocation context, so an agent has no routing signal.

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