update_project_memory

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

Describes mutation behavior (append, refresh, update next_step) but lacks details on potential side effects, authentication needs, or limits. With no annotations, description carries full burden and is adequate but not thorough.

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 plus bulleted arg list, front-loads purpose and usage. No filler, every sentence earns its place.

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?

Explains primary effect and workflow integration. References sibling tool load_project_context. Lacks details on return value or error conditions, but output schema exists so not required.

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 has 0% description coverage, but the description's Args section adds meaning: explains project_id as slug, what_was_done as concise summary, next_steps as optional field update. Goes beyond schema property names.

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?

States specific action: 'Append a session summary to a project's history and refresh its prompt memory.' Clearly distinguishes from sibling 'load_project_context' by specifying it is for end-of-session updates.

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 says 'Call this at the end of any work session on a project.' Also explains how it feeds into load_project_context(), providing context for why and when to use.

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