store

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

With no annotations, the description discloses key behaviors: encryption algorithm (AES-256-GCM), random IV generation per encryption, and overwriting existing values. This provides good transparency, though it could mention side effects like potential performance impact.

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 a single, tightly worded sentence that efficiently conveys the core action, encryption details, and overwrite behavior with no superfluous words.

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?

While the description covers encryption and overwriting, it lacks information about the return value (e.g., success indicator or ciphertext), potential error conditions, or prerequisites like initialization. For a tool with no output schema, this is a notable gap.

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 descriptions 'Item name.' and 'Plaintext value to encrypt.' The tool description adds encryption context (AES-256-GCM) but does not elaborate further on parameter formats or constraints beyond the schema. Baseline of 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 states it encrypts a value with AES-256-GCM and saves it under a given key, clearly indicating a write operation. This distinguishes it from siblings like fetch (read) and remove (delete).

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 implies usage for storing encrypted values and mentions overwrite behavior, but lacks explicit guidance on when to use vs. alternatives like lock or init. No exclusions or prerequisites are given.

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