memory_export_advanced

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as whether the tool is read-only, modifies memory, supports specific formats, or has side effects. The description is too minimal to inform an agent about behavior.

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 sentence, which is concise, but it sacrifices completeness and clarity. It is front-loaded but lacks detail. Every word earns its place, but the overall informativeness is low.

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?

Given the tool has a nested object parameter and no output schema, the description is incomplete. It does not explain what formats are supported, how options work, or what the output looks like. The complexity demands more explanation than provided.

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 50% (outputPath described, options not). The description mentions 'multiple formats and options' but does not explain the 'options' object's properties or valid values. It adds no meaningful detail beyond the schema for the parameters.

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 'Advanced memory export with multiple formats and options', which indicates the tool performs an export operation. However, 'advanced' is vague and does not specify what distinguishes it from the simpler 'memory_export' sibling. The purpose is clear but lacks specificity and differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'memory_export'. There is no mention of prerequisites, context, or exclusions. The description fails to help an agent decide when to invoke this tool.

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