mnemos_store

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

The description says 'Store a new memory' but annotations indicate destructiveHint=true, implying potential data destruction. The description does not address this contradiction or provide any side-effect context, such as overwriting behavior or resource implications.

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?

At 6 words, it is very concise but may be too brief for a tool with 7 parameters and no output schema. It front-loads the purpose but lacks supporting detail, making it adequately concise but not optimally informative.

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 complexity (7 params, no output schema), the description fails to mention return values, confirmation behavior, or the consequences of the 'destructive' annotation. It is incomplete for an agent to use effectively without additional context.

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?

All 7 parameters have schema descriptions (100% coverage), so the description adds no additional meaning. It does not elaborate on how parameters like 'type' or 'tags' affect storage behavior beyond the schema.

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 states the verb 'store' and resource 'memory' in 'Mnemos', indicating a creation operation. However, it does not differentiate from sibling tools like mnemos_update or mnemos_relate, leaving ambiguity about when to use this tool over others.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context for choosing store over related tools like compile or update.

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