mnemos

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

Fails to explain the destructiveHint: true annotation - description presents as a benign query operation without clarifying what data is destroyed or modified. Mentions token budget constraint which adds some behavioral context beyond 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?

Single efficient sentence puts the action first. However, given the destructive annotation and complex sibling ecosystem, extreme brevity becomes a liability rather than a virtue.

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?

Lacks output schema explanation and fails to clarify destructive behavior indicated by annotations. In a 7-sibling toolset, description needs to better define this tool's specific role in the memory management workflow.

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?

With 100% schema description coverage, the schema fully documents all parameters. Description mentions 'token budget' which aligns with max_tokens but adds no significant semantic detail 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?

Uses specific verb 'Assemble' with resource 'context' and mentions token budget constraint. Slightly vague on how it differs from mnemos_search or mnemos_get, but 'assemble' implies a relevance-ranked collation versus simple retrieval.

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?

Provides no guidance on when to use this tool versus siblings like mnemos_search or mnemos_get. No mention of prerequisites or conditions for use.

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