memento_search

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

No annotations are provided, and the description does not disclose whether the tool is read-only, has side effects, or any safety information. It only explains search modes without behavioral details like performance or resource consumption.

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 very concise, using a single sentence to state purpose and list modes. It is front-loaded with the key verb and resource, but could be more structured and informative without adding verbosity.

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 of 7 parameters (including nested objects) and no output schema, the description is insufficient. It does not cover return format, filter behavior, or the role of trace and active_context, leaving the agent with incomplete understanding.

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?

Schema coverage is only 14% (query has description). The description adds meaning for the mode parameter by explaining the modes, but the other 6 parameters (limit, filters, trace, active_context, workspace_root) lack any additional description, leaving a significant gap.

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 'Search memories' as the primary function and distinguishes three modes (basic, advanced, explain), differentiating it from sibling tools like memento_remember (for creating memories) and memento_audit_dependencies.

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 lists modes but does not provide explicit guidance on when to use this tool versus alternatives or when to choose each mode. Usage is implied by the name and hierarchy, but no exclusions or contextual cues are given.

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