remember_decision

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

No annotations provided; description only states basic write action without detailing behavior like overwrite policy, visibility, or persistence beyond 'record'.

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?

Single sentence, front-loaded with action and resource, no wasted 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?

Covers purpose and parameter hints adequately for a write tool with no output schema; could clarify overwrite vs append behavior.

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 meaning beyond schema: body should contain 'what, why, evidence' in markdown, files are 'repo-relative', title is 'one-line summary'.

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 specific verb 'Record' and clear resource 'important design or implementation decision with rationale', distinguishing it from siblings like 'remember_failed_attempt' which focuses on failures.

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?

Implies usage when preventing relitigation, but lacks explicit when-not-to-use or comparison to alternatives like 'recall_project_context'.

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