save_context

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

With no annotations, the description must bear the weight of behavioral disclosure. It explains the tool persists context to memory and captures file changes, but does not mention whether repeated calls overwrite or append, if it requires specific permissions, or what happens after saving. This is acceptable but leaves some side-effect ambiguity.

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 sentences, directly front-loaded with the action, and every clause earns its place. It avoids redundant restating of parameter names and gets straight to the point. 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?

For a no-output-schema, no-annotations tool with five optional parameters, the description covers purpose, typical usage timing, and what is captured. It does not differentiate from sibling checkpoint_context or describe the return value, but it is sufficiently complete for a simple save operation.

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?

The schema already provides 100% coverage for all five parameters, so the baseline is 3. The description adds value by mentioning 'file changes' as a captured element, which is not a parameter but indicates automatic behavior, and 'decisions, learnings' align with the decisions and learnings parameters. This extra context meaningfully enriches the schema.

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 opens with a specific verb+resource: 'Save the current workflow context to memory.' It then clarifies what is captured (decisions, learnings, file changes) and the purpose (future sessions), clearly distinguishing it from siblings like get_memory and restore_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?

The description provides clear usage context: 'Use this to persist important context before completing or rolling back a feature.' This tells the agent when to invoke it, though it does not explicitly mention alternatives or exclusions. The guidance is sufficient for most workflows.

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