Save Context

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal that the tool writes to a specific file path in the current working directory, which is helpful. But it does not disclose whether existing files are overwritten, whether directories are created implicitly, or any other side effects, such as the absence of a return value.

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?

The description is a single, tight sentence that front-loads the primary action and includes concrete content examples. Every word contributes to clarity, and there is no redundancy or padding.

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?

The description covers the essentials for a simple save operation, with fully documented parameters and a clear destination file. However, it omits overwrite semantics (what happens if the topic already exists) and gives no nod to the sibling read_context for retrieval. Given that there are no annotations or output schema, this leaves a notable but minor 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 description coverage is 100% for both required parameters. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline of 3 is appropriate: the schema fully documents topic naming and markdown content.

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 states a specific verb ('persist'), a resource ('markdown project context, architectural rules, or decisions'), and a precise destination ('.opencontext/<topic>.md in the current working directory'). It clearly identifies a write operation and is readily distinguishable from the read_context sibling.

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 verb 'persist' and the file-target phrasing imply the use case: save context content for later retrieval. However, the description does not explicitly state when to use this tool versus read_context, nor does it mention that read_context is the appropriate counterpart for reading the saved files.

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