CPersona

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

Adds valuable format context (JSONL) and scope (includes profiles/episodes) beyond the readOnlyHint annotation. However, fails to disclose file I/O behavior (e.g., whether it overwrites existing files at output_path) or if the operation is blocking vs. async.

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?

Single, efficient sentence of 12 words. Front-loaded with verb action, zero redundancy, and every clause earns its place by conveying scope, format, or purpose.

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?

Sufficiently complete for tool selection given simple parameters and readOnly annotation. Mentions key exportable entities and optional embedding inclusion, though brief mention of relationship to 'import_memories' would strengthen contextual completeness.

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 a baseline of 3. Description reinforces output_path's purpose by mentioning 'JSONL file' and clarifies agent_id scope by listing the three exported entity types, but adds no semantic detail about parameter interactions (e.g., that empty agent_id exports all).

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' with specific resources (memories, episodes, profiles) and output format (JSONL). Implies bulk read operation distinguishing from singular access tools like 'get_profile' or 'recall', though lacks explicit contrast with sibling 'import_memories'.

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?

Provides implied usage context ('for backup or portability') but lacks explicit guidance on when to prefer this over 'import_memories' or individual read tools, and does not state prerequisites like directory permissions for the output_path.

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