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

No annotations exist, so description carries full burden. It reveals three actions (create, checkpoint, restore) and mentions 'across conversations', signaling persistence scope. However, it does not disclose details like whether checkpoints are retained indefinitely, if there are size limits, or side effects like overwriting previous checkpoints when creating a new one. Adequate but not rich.

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 sentence that says exactly what the tool does. Front-loaded with the key concept (managing sessions for checkpoint/restore). No filler, no redundancy with schema. Perfectly concise.

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 output schema exists (agents can inspect return structure) and full parameter documentation, the description covers the essential purpose. It is a generic session management tool, not overly complex. The one-line description plus rich schema is sufficient. Could mention that sessions persist across conversations, but that is already implied.

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 100%, but the description adds no parameter-level detail beyond the schema. Baseline starts at 3 for full coverage; the description earns a 4 because the schema itself is very descriptive (documents which params are for which action, defaults, required status, and data types), so the description doesn't need to repeat. Minimal added value, but the schema does the work.

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 clearly states the tool manages sessions for checkpoint/restore of agent state. It distinguishes from memory-related sibling tools which focus on recall/store/update operations, not session lifecycle management.

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?

The description implies the tool is for saving and restoring agent state across conversations but does not explicitly state when to use this vs memory tools. No guidance on when to create vs checkpoint vs restore, or prerequisites like needing a session_id for checkpoint/restore. The context of 'across conversations' is helpful but implied.

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

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

With no annotations provided, the description must disclose behavioral traits. It mentions deletion and idempotent extraction in parameter descriptions, but the main description omits side effects, authorization requirements, or whether actions are read-only. The term 'administrative' is vague.

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, short sentence that front-loads the key concept 'Administrative operations'. It is efficient, though the list after the colon could be better structured for readability.

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's complexity (11 parameters, 7 actions) and the existence of an output schema, the description is too brief. It does not provide a high-level overview of how the actions interrelate or the typical usage workflow, leaving gaps that the schema alone must fill.

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 100%, so the input schema already documents all parameters and their semantics (e.g., action enum values). The main description adds no additional meaning beyond listing the categories, so the baseline score of 3 is appropriate.

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 'Administrative operations' which clearly differentiates it from sibling tools like recall_memories and store_memory. However, it lists multiple categories (stats, background jobs, etc.) rather than a single verb+resource, making the purpose broad but distinguishable.

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. The description does not mention when not to use it or how to choose among the many actions. Users must infer from the tool name and enum values.

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

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

No annotations are provided, so the description must carry the burden. It does disclose the exclusive-selector constraint and the expand_links graph-neighbor behavior. However, it does not explicitly state read-only safety, snippet truncation vs. full content, or how multiple modes interact with filters. The verb 'Retrieve' implies non-mutating behavior, but additional behavioral context beyond the schema is limited.

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 compact and front-loaded: the first sentence immediately conveys the three access modes, and the second sentence adds the selector constraint and graph expansion tip. Every sentence contributes information without bloat or repetition, making it highly scannable.

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's high complexity (18 parameters) and the presence of a rich output schema, the description does not need to explain every filter or return field. It covers the core access patterns, the mandatory-selector constraint, and the optional graph expansion feature. The schema and output schema handle the remaining details, so the description is sufficiently complete for an agent to understand the tool's main behavior.

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%, so the baseline is 3. The description adds value by stating the cross-parameter exclusivity rule (exactly one of query, memory_id, or entity) and that expand_links>0 includes graph neighbors. These constraints are not uniformly obvious from individual parameter descriptions, so this is a meaningful enhancement over the schema.

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 starts with the specific verb 'Retrieve memories' and enumerates three distinct retrieval modes (hybrid/keyword/semantic search via query, exact fetch via memory_id, entity lookup via entity). This clearly differentiates the tool from its write/manage/admin siblings (store_memory, update_memory, manage_session, memory_admin).

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?

The description gives a clear within-tool usage rule ('Exactly one selector — query, memory_id, or entity — must be provided') and explains when expand_links is useful. However, it does not explicitly state when to choose this tool over alternatives, such as 'use this for reading existing memories' vs. 'use store_memory to create new ones'. The guidance is implied by context rather than stated.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions optional scoping, embedding, and links, but does not disclose operational traits such as idempotency, permissions required, side effects of invalid inputs (e.g., non-existent link targets), or any constraints on memory creation. For a tool with 7 parameters, this is insufficient.

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 concise sentence of 14 words, stating the core action and key optional features. It is front-loaded with the verb and resource, containing no filler or redundant information.

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 7 parameters, 2 required, an output schema, and no annotations, the description covers the high-level purpose but omits details about behavior (e.g., whether it returns the created memory), error conditions, or constraints on required parameters. The output schema may fill some gaps, but for a creation tool, more context would improve agent confidence.

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 100%, so the baseline is 3. The description adds context by naming 'agent/session scoping' (mapping to agent_id/session_id), 'graph links' (mapping to links), and 'semantic embedding' (implied by memory_type). While helpful, it does not provide additional semantic depth beyond what the schema already documents.

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 clearly states the action ('Store a new memory') and identifies the resource as a memory. It distinguishes this tool from siblings like recall_memories (retrieval), update_memory (modification), manage_session (session management), and memory_admin (admin tasks) by positioning it as the creation action.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or direct users to other tools for related tasks. The sibling tool names provide implicit context, but the description itself lacks any usage direction.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It introduces 'optimistic locking' as a key behavior, which is useful for agent reasoning. However, it does not explain what happens on version conflict, whether the operation is idempotent, or any authentication/authorization requirements. The description adds some value beyond the schema but is not comprehensive.

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, concise sentence that is front-loaded with the core action. It contains no filler words and is easy to parse. However, it could be slightly more structured (e.g., listing key aspects) without losing conciseness.

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's complexity (6 parameters, optimistic locking, an output schema), the description is too brief. It fails to explain the locking mechanism, what happens on conflict, how to use the output schema, or any other contextual details. The description leaves significant gaps that the agent must infer from parameter names alone.

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 100%, so the baseline is 3. The description does not add any additional meaning to the parameters beyond what is already documented in the schema. The term 'optimistic locking' relates to the 'expected_version' parameter, but this connection is not elaborated. Therefore, no extra semantic value is provided.

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 clearly indicates the verb 'Update' and the resource 'memory'. It adds a specific behavioral qualifier ('optimistic locking for concurrent agent safety') that distinguishes it from basic update operations. However, it does not explicitly differentiate from the sibling tool 'store_memory' (which likely creates a new memory), leaving some ambiguity about when to use each.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'store_memory', 'recall_memories', or 'memory_admin'. It does not mention prerequisites, limitations, or conflict scenarios. The optimistic locking mention implies usage in concurrent environments, but without explicit directives, the agent must infer appropriateness.

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