dakera_store

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

Discloses importance default and critical range with decay hint, but no annotation burden exists. However, omits details on other parameters like expires_at, session_id, and return behavior.

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?

Two concise sentences each carrying unique information; no redundancy or 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?

With 7 parameters and no output schema or annotations, the description covers only importance and tags, leaving memory_type, session_id, expires_at, and return value unexplained.

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?

Adds value beyond schema by specifying importance default and critical range, and highlighting optional tags. Schema coverage is high (86%), so baseline is 3; description provides extra nuance.

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 tool persists a new memory with importance and tags, specifying verb and resource. It differentiates from retrieval tools but doesn't explicitly contrast with batch operations among siblings.

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 when to use ('save facts, decisions, or context') but lacks when-not-to-use or explicit alternatives from the sibling list.

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