memory_stats

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

The annotation readOnlyHint already indicates no side effects. The description adds value by specifying the return format (JSON string) and example fields, although it uses 'etc.' which slightly reduces completeness. No contradictions with annotations.

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 extremely concise at two sentences. It front-loads the primary purpose and immediately follows with the return value description. Every sentence adds unique value without redundancy.

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 tool has no parameters, annotations cover read-only behavior, and an output schema exists (not shown but indicated), the description provides sufficient context to understand what the tool returns and its scope, making it complete for agent selection.

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 are no parameters, so the description does not need to add parameter-level semantics. The baseline for zero parameters is 4, and the description adequately covers the tool's operation without requiring further parameter clarification.

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 clearly specifies the verb 'Get' and the resource 'memory statistics for the current account'. It provides concrete details about the returned data (total memories, average importance, tag distribution), which distinguishes it from siblings like 'memory_health' or 'list_memories'.

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 implies usage for obtaining memory statistics of the current account, but it does not provide explicit guidance on when to use this tool over alternatives (e.g., 'memory_health') or state any exclusions, such as when not to use it.

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