memory_stats

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention whether this is a read-only operation, potential side effects, authentication requirements, or return format. It only says 'Get vault statistics,' leaving the agent to infer behavior.

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 is front-loaded with the verb 'Get' and resource. Every word earns its place, and there is no wasted text.

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?

The tool is simple (no parameters) but has no output schema. The description fails to clarify what 'vault statistics' actually are (e.g., count of memories, storage usage, etc.). This lack of detail leaves the agent uncertain about the tool's output, making the description incomplete for a tool with no other structured information.

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, and the schema coverage is 100% (empty properties). Per the baseline for 0-parameter tools, the description does not need to explain parameter semantics. The mention of 'vault statistics' adds a slight hint about what the output relates to, but no parameter-specific information is 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 'Get vault statistics' uses a specific verb 'get' and resource 'vault statistics', which clearly differentiates it from sibling tools like memory_list (listing memories) or memory_search (searching). However, it does not specify what the statistics include, so it is clear but slightly vague.

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 guidance on when to use this tool versus alternatives. The description simply states what it does without providing context on use cases, prerequisites, or when another tool would be more appropriate.

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