Agent Memory Bridge

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

No annotations provided, so description carries full disclosure burden. Adds valuable context about external portability and avoiding direct database access, but omits critical safety profile (read-only vs. destructive), idempotency, or whether 'export' implies copy or move semantics. 'Move memory' phrasing slightly ambiguous regarding source data retention.

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 well-structured paragraphs with zero redundancy. First sentence establishes core function; second paragraph delivers specific usage contexts. Front-loaded and efficient—every sentence earns its place without repeating schema details.

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?

Rich 7-parameter schema with 100% coverage and existing output schema reduces description burden. Description adequately covers the 'why' and 'when' for this complex filtering/export tool, though could acknowledge the batch nature (limit parameter) or signal-specific filtering capabilities.

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 coverage is 100%, establishing baseline 3. Description provides conceptual framing ('human-readable snapshot') that aligns with format options, but does not add parameter-specific guidance, syntax examples, or filtering logic beyond the comprehensive schema documentation.

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?

Clear verb (export) and resource (bridge content) with scope (readable/portable format). Distinguishes from siblings like 'recall' and 'browse' by emphasizing external use cases and portability, though could explicitly contrast with internal retrieval tools.

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?

Explicit 'Use this tool when...' statement lists three concrete scenarios: external namespace inspection, human-readable snapshots, and inter-system data transfer. Lacks explicit negative constraints (when not to use) or named alternatives, but effectively guides selection via positive use cases.

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