memory_stats

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

There are no annotations provided, so the description carries the full burden. It implies a read-only operation via 'Get', but does not explicitly state that it is non-destructive, what data it returns, or any side effects or permissions. The behavior is only minimally transparent.

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, concise sentence that directly states the purpose. It adheres to the principle of brevity and clarity, with no extraneous words or structure.

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?

Given the lack of an output schema, the description is incomplete in explaining what the agent should expect from the tool. It does not say what kind of statistics are returned (e.g., counts, sizes, metadata) or how they might be used. An agent would need additional context to correctly interpret the result.

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 has zero parameters, so the schema coverage is 100%. Per the baseline, a score of 3 is given when the schema fully documents all parameters. The description does not add any additional meaning about parameters, but none are needed.

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 states a clear action 'Get' and an object 'graph statistics', but the object is vague. It does not specify what kind of statistics, which graph, or how they are presented. It is better than a tautology but lacks specificity to fully distinguish from similar tools like memory_explain or memory_recall.

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 description provides no guidance on when to use this tool versus its siblings. It does not mention any conditions, prerequisites, or alternatives. An agent would have to infer from the name alone that it is for retrieving statistics, with no clear differentiation from other memory tools.

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