working_memory_set

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

No annotations provided; the description fully compensates by disclosing automatic expiry with default TTL (86400s), overwrite behavior without error, and project-level scoping.

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?

Three sentences with front-loaded core action. Each sentence adds essential info: purpose+expiry, overwrite detail, usage guidance and alternative. No fluff.

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?

No output schema; description does not state what the tool returns on success. However, for a simple set operation, this is a minor gap given the solid behavior and usage coverage.

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 description coverage is 100%, baseline 3. Description adds value by explaining default TTL, overwrite behavior, and giving a key format example (e.g., 'debug_flag').

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 that the tool stores a transient key-value entry scoped to the current project, distinguishes it from update_state (persistent storage), and provides specific use cases like debug flags and temporary task context.

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?

Explicitly tells when to use (debug flags, temporary task context) and when not to use (data that must survive session restart, recommending update_state instead). Also mentions overwrite behavior without error.

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