backup

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

With no annotations, the description carries the full burden. It discloses the side effect (creates a file), the destination path, the content scope (payloads + vectors), and the automated schedule. It stops short of describing overwrite/collision behavior or return value, which would make it fully transparent.

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 short sentences each carry distinct value: what is created, where it is saved, and when to use it manually. There is no filler or redundancy.

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 zero-parameter tool with no output schema, the description covers the core invocation details: action, scope, destination, schedule, and on-demand intent. It could mention the success/return value and existing-backup behavior, but these are minor gaps for a simple backup 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 tool has zero parameters, so the schema is complete by default and no parameter documentation is needed. The description's mention of 'full backup' and 'payloads + vectors' adds context that an agent does not need parameters to act on.

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 a specific verb ('Create'), a clear resource ('all memories'), and a concrete artifact ('JSON file'), while specifying it includes payloads and vectors. This is unambiguous and distinct from sibling operations like restore, remember, or recall.

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 frames the tool as manual on-demand backup ('use this for manual backup on demand') and notes that the same operation runs automatically every 24h. It does not name alternative tools or exclusions, but it gives enough context to select it over unrelated siblings.

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