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

The description discloses behavioral traits beyond annotations: storage as key-value pair scoped by identifier, persistence duration for anonymous sessions (24 hours) vs authenticated users, and cross-session availability. These are not available in annotations and add critical context.

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 four sentences, front-loaded with the primary purpose, and each sentence provides essential information (when to use, storage mechanics, persistence, companion tools). No redundancy or unnecessary detail.

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?

Despite lacking an output schema, the tool is simple (2 required params) and the description sufficiently covers purpose, usage triggers, scoping, persistence, and pairing with recall/forget. It gives an agent everything needed to invoke appropriately.

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 covers 100% of parameters with descriptive examples. The description does not add substantial new parameter semantics beyond the schema, though it reiterates the kind of data to store (e.g., resolved ticker, target address). Baseline 3 is appropriate given high schema coverage.

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 'Save' with a clear resource 'data the agent will need to reuse later', and explicitly differentiates from siblings by mentioning 'Pair with recall to retrieve later, forget to delete.' It clearly states the tool persists key-value pairs.

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?

It provides explicit when-to-use guidance: 'Use when you discover something worth carrying forward' with concrete examples, and it contrasts with recall/forget as complementary operations. It also clarifies persistence rules for authenticated vs anonymous users, covering context.

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