Memphora

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

No annotations are provided, so the description carries the full burden. It describes the tool's purpose and usage context but lacks details on behavioral traits such as storage limitations, persistence duration, privacy implications, or error handling. The description doesn't contradict any annotations, but it misses key operational details for a storage tool.

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 front-loaded with the core purpose, followed by usage guidelines and examples. Every sentence adds value without redundancy, making it efficient and well-structured for quick understanding.

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's moderate complexity (storage operation with 2 parameters) and no output schema, the description covers purpose and usage well but lacks details on return values or behavioral aspects like success confirmation. It's mostly complete but could benefit from information on what happens after storage.

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?

The input schema has 100% description coverage, providing clear documentation for both parameters. The description adds value by emphasizing that the content should be 'a complete, self-contained fact' and giving examples that illustrate the semantics, though it doesn't explicitly detail parameter usage beyond what the schema covers.

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 explicitly states the verb ('Store') and resource ('important information about the user for future recall'), making the purpose specific and clear. It distinguishes this tool from its siblings by focusing on storing user information, unlike deletion, extraction, listing, or searching operations.

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 provides explicit guidance on when to use this tool ('when the user shares personal details, preferences, facts about themselves, or explicitly asks you to remember something') and includes concrete examples. This clearly differentiates it from alternative tools like memphora_search or memphora_list_memories.

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