CPersona

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

Excellent disclosure of idempotency mechanism ('via msg_id deduplication') beyond the boolean annotation flag. This explains HOW duplicate prevention works. Could improve by clarifying conflict resolution behavior (skip vs update) for existing records.

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 efficient sentences with zero waste. First sentence establishes core operation; second sentence front-loads critical behavioral trait (idempotency mechanism). Every word earns its place.

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?

Strong for a 3-parameter import tool with complete schema coverage. Covers operation scope, file format, and idempotency. Minor gap: lacks description of return values or import summary (count of processed records) given no output schema exists.

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?

With 100% schema description coverage, the schema fully documents all parameters (input_path, target_agent_id, dry_run). Description references 'JSONL file' reinforcing input_path but does not add syntactic or semantic details beyond the schema's explanations.

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 specific verb 'Import' with explicit resource scope (memories, episodes, profiles) and source format (JSONL). Distinguishes from sibling 'export_memories' and single-record operations like 'store' or 'update_profile'.

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?

Implies bulk import usage via 'JSONL file' mention and hints at retry-safety through idempotency disclosure. However, lacks explicit guidance on when to prefer this over 'store' for individual records or prerequisites like file format requirements.

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