save_decision

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

Description mentions adding a structured tag and JSON blob, going beyond annotations which only indicate non-read-only, non-destructive, and non-idempotent. It does not specify whether it creates new entries or updates existing ones, but the 'Adds' phrasing implies creation.

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 that are directly relevant, with no redundancy or filler.

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?

Given the tool's complexity (8 params, nested objects), the description adequately covers the core purpose and usage context. It does not describe return values, but no output schema exists, so that is not a 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 covers 75% of parameters with descriptions. The tool description reiterates the main required components but does not clarify the missing 'project' or 'tags' parameters beyond what the schema lacks. No additional per-parameter semantics are provided.

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?

Clearly states the tool saves a structured architectural decision with specific components (options, criteria matrix, rationale, discarded). Also notes it adds a structured tag and JSON blob, distinguishing it from plain memory_save.

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 directs usage for Creative-phase outputs and mentions that plain type=decision memory_save still works as an alternative, providing clear when-to-use guidance.

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