doctor_memoryIdentify memory health issues by reporting duplicate, deleted, expired, conclusion, invalid-record, and index health counts without altering data.
Report duplicate, deleted, expired, conclusion, invalid-record, and index health counts without changing data.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Explicitly declares read-only behavior ('without changing data'), which is critical. Lists specific categories reported, though does not detail what 'index health' means or any performance considerations.
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?
Single sentence of 9 words, perfectly concise and front-loaded with key information.
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?
Adequately covers the tool's purpose and scope given its simplicity (0 params, no output schema). Lists all reported categories, though lacks definitions for each metric.
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?
No parameters exist; schema coverage is 100%. Description adds no parameter info as none are needed, meeting baseline for zero-parameter tools.
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?
Clearly states verb 'report' and resource 'memory store health counts' for specific categories (duplicate, deleted, etc.), distinguishing from siblings that perform different operations like deletion or search.
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?
Implies diagnostic use via 'report' and 'without changing data', but lacks explicit when-to-use guidance compared to alternative tools like ask_memory or search_memory.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.