saihm_remember

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

No annotations exist, so the description must disclose behaviors. It mentions 'persistent encrypted memory' but omits details like whether overwriting occurs, data limits, or authentication requirements.

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 one concise sentence, but it lacks front-loaded structuring. It wastes no words but could benefit from additional context without becoming verbose.

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?

For a simple store tool with one parameter and no output schema, the description is minimally adequate. However, it leaves questions about persistence details and integration with sibling tools, which should be addressed.

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 100% with a single parameter 'content' described as 'Information to remember' both in schema and description. The description adds no new meaning beyond the schema, resulting in a baseline score.

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 uses a specific verb 'store' and resource 'information to SAIHM persistent encrypted memory', clearly indicating the action and storage type. It distinguishes from siblings like 'forget' and 'recall' but lacks specificity about what kind of information.

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 guidelines for when to use this tool versus alternatives. With siblings like 'saihm_forget' and 'saihm_recall', the description should clarify scenarios (e.g., 'Use to store a fact; use recall to retrieve it').

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