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

Annotations indicate a write operation (readOnlyHint=false), and the description confirms this with 'Store'. It adds the advice to use 'concise model-readable facts, not conversation prose', which is useful content guidance. However, it does not disclose persistence behavior, whether it overwrites existing checkpoints, or any side effects on other memory tools. No contradiction with annotations.

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 two sentences, front-loaded with the core purpose and followed by a concise content guideline. No wasted words, though the second sentence could be integrated more structurally.

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 7 parameters (3 required), no output schema, and minimal behavioral context, the description is inadequate. It lacks parameter semantics, usage guidance, and any explanation of how the checkpoint integrates with the broader memory system. An agent would struggle to call this correctly without external knowledge.

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 0%. The description mentions 'structured task checkpoint' but does not explain any of the 7 parameters (summary, evidence, decisions, next_steps, session_id, constraints, project_root). The required fields are entirely undocumented, forcing the agent to guess their semantics from names alone.

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 verb 'store' and the resource 'structured task checkpoint' with a purpose ('for later continuation'). It distinguishes the concept from siblings like memory_remember by implying a checkpoint is a snapshot of progress, but it does not explicitly name alternatives or differentiate beyond that.

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_remember or memory_recall. The description implies a use case (continuation) but gives no exclusions or explicit conditions. An agent must infer when a checkpoint is appropriate.

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Read' wording aligns with that safety profile. It adds some behavioral context by noting the packet is 'bounded' and that output is machine-readable facts without NL translation, but it does not explain limits, errors, or what happens when the token budget is exceeded.

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 short sentences with no filler. The core action is front-loaded, and the additional return-format detail earns its place. Despite the unexplained acronym, the description is appropriately sized.

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?

With no output schema and three parameters at 0% schema coverage, the description needs to explain how to call the tool and what to expect. It only covers the general return style, leaving query semantics, token budget behavior, and the meaning of project_root largely to inference.

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 0%, so the description must compensate for the undocumented parameters. It does not explain project_root, query, or token_budget explicitly; 'bounded' hints at token_budget and 'engineering packet' hints at project_root, but these are too indirect to guide correct invocation.

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 a clear verb and resource: 'Read a bounded EIR/1 engineering packet.' It also adds a distinguishing output trait, 'machine-readable facts without natural-language translation,' which helps separate it from natural-language-oriented memory tools. However, 'EIR/1' is unexplained and sibling differentiation is implicit rather than explicit.

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 given about when to use this tool instead of siblings like memory_recall or memory_status. The phrase 'engineering packet' weakly implies context, but there is no stated selection criterion, prerequisite, or exclusion.

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?

The description meaningfully refines the annotations: destructiveHint=true could imply irrecoverable deletion, but the description clarifies the operation is a tombstone append where prior history remains auditable — a genuinely non-obvious behavioral fact beyond what readOnlyHint=false/idempotentHint=true/destructiveHint=true convey. It stops short of explaining the effect on future recalls, but the core safety-and-mechanism profile is well covered.

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?

A single 10-word sentence with zero filler; the mechanism ('Append a tombstone') is front-loaded and the key behavioral property ('prior history remains auditable') follows immediately. Every phrase 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?

The mechanism and auditability guarantee are covered, but the tool mutates state with no output schema and the agent is left without knowledge of return shape, the effect on subsequent memory_recall calls, or how the optional session_id/project_root parameters combine with the required scope/topic. For a 4-parameter mutation this is workable but has clear operational gaps.

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 0%, so the description bore the full burden of explaining scope (enum user/project/session), topic, session_id, and project_root — and it only touches 'topic' implicitly via 'for a topic'. The interplay of scope, session_id, and project_root is entirely undocumented, and the description fails to compensate for the schema's lack of param descriptions.

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 a specific mechanism — 'Append a tombstone for a topic' — with a clear verb (append) and resource (tombstone for a topic), and the auditability clause distinguishes this from a hard delete, which meaningfully clarifies what 'forget' does. However, 'tombstone' is jargon that isn't unpacked, and it doesn't explicitly differentiate from siblings like memory_remember or memory_recall.

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 given on when to use memory_forget versus any of its seven siblings, when forgetting is appropriate, or what prerequisites apply (e.g., whether the topic must exist, how scope selection affects behavior). An agent must infer usage entirely from the tool name and the one-line mechanism.

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?

Annotations already carry idempotentHint=true, destructiveHint=false, and readOnlyHint=false, which cover the safety profile. The description adds deterministic behavior and the output format, but it does not disclose side effects such as writing to memory, whether existing facts are overwritten, or any operational requirements. It adds some context without contradicting annotations.

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 compact sentence with no filler. It front-loads the main action and includes only meaningful qualifiers ('deterministically', 'compact', 'no model summary'), making it efficient and easy to parse.

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?

For a tool that is not read-only (readOnlyHint=false), with no output schema and two parameters whose semantics are unexplained, the description is incomplete. It doesn't explain where the EIR/1 facts are stored, how results are returned, what the size/file limits control, or how idempotency manifests. An agent would need to guess key operational details.

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 0%, so the description must compensate by explaining parameter meaning. It only implies that 'project' maps to project_root and says nothing about max_files or max_file_bytes, leaving the agent to guess what these limits do. This is minimal compensation and insufficient for two of the three 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 clearly states a specific action (deterministically scanning a project) and output (EIR/1 facts and dependency edges). It also distinguishes itself from model-based siblings like memory_remember by explicitly stating no model summary is used, so an agent can tell what this tool does relative to the family.

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 usage for deterministic project scanning by contrasting with model summaries, but it never explicitly names when to use this tool versus siblings like memory_remember or memory_engineering_context, nor does it mention when not to use it. This is implied guidance, not explicit.

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?

Annotations already provide idempotentHint=true and destructiveHint=false, and the description adds the important behavioral nuance of 'reuse', implying existing state is not destroyed. It also discloses the specific file affected, which is useful beyond the raw annotation values.

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 front-loaded sentence with no filler. Every word contributes to identifying the action, the object, and the location, which is appropriately concise for a simple two-parameter tool.

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?

For a low-complexity tool with supportive annotations, the core behavior is communicated adequately. However, there is no mention of what happens when the file already exists beyond 'reuse', no description of the optional name parameter, and no indication of what the tool returns or confirms.

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 0%, so the description carries the burden, but it only indirectly hints that project_root is the location containing .scoped-memory. The optional 'name' parameter is not explained at all, leaving its purpose and format ambiguous.

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 a specific verb ('Create or reuse'), a clear resource ('stable project identity'), and the exact location ('.scoped-memory/project.json'). This clearly distinguishes it from siblings like memory_ingest_project or memory_status.

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 given about when to call this tool versus alternatives, such as before ingesting a project or when a project identity is missing. The sibling tools are listed in context, but the description does not reference them or state the conditions that select this one.

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?

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: output is deterministic, token-budgeted, and project-scoped unless inheritance is explicit. This is modest value beyond annotations, with no contradiction.

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 two short sentences with no filler; the primary action is front-loaded and the second sentence adds a relevant scoping constraint. Every word earns its place, and the structure is easy to scan.

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?

For a 6-parameter tool with no output schema, this description is too sparse for an agent to invoke it correctly. It omits what 'context packet' means, what query and scopes do, which fields are needed, and what the tool returns. The project-exclusion note is a small fragment of the needed context.

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 0%, so the description needed to compensate by explaining the six parameters. It only hints at token budgeting and inherited project IDs; query, scopes, session_id, and project_root are left entirely unexplained. This is far below what a 0%-coverage tool requires.

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 identifies a concrete action and output ('Build a deterministic token-budgeted context packet') and adds a project-scoping rule, so a basic purpose is present. However, 'context packet' is vague jargon and the recall/retrieval nature is only implied by the tool name. It does not distinguish this from sibling tools such as memory_engineering_context.

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?

There is no guidance on when to call this tool versus siblings like memory_engineering_context, memory_remember, or memory_status. The only additional statement—that other projects are excluded unless inherited—describes a behavioral constraint, not a usage condition or alternative selection.

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?

The description discloses a non-obvious behavior: 'Reusing a topic supersedes it without rewriting history,' which adds meaningful context beyond the sparse annotations. Since readOnlyHint, idempotentHint, and destructiveHint are all false, this explanation helps clarify the actual write semantics without contradicting them.

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 two sentences, with the purpose front-loaded and the behavioral caveat in the second sentence. It is appropriately compact, though the phrase 'supersedes it without rewriting history' is somewhat ambiguous.

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?

With 8 parameters, no output schema, and no parameter descriptions, the description leaves too much unspecified: meaning of required fields, effect of optional fields like metadata and importance, return value, and how the 'history' mechanism works. It is not complete enough for reliable tool invocation.

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 0%, and the description names no parameters directly. It indirectly mentions 'topic' and scope values, but does not explain content, metadata, tags, importance, session_id, or project_root, so it does not compensate for the lack of parameter descriptions in 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 uses the specific verb 'Append' and identifies the resource as user/project/session memory, which is clear. It adds a behavioral nuance about topic reuse, but it does not explicitly differentiate from sibling tools like memory_ingest_project or memory_engineering_context, so it lacks full sibling 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?

There is no guidance on when to use this tool versus memory_recall, memory_forget, memory_ingest_project, or memory_engineering_context. The description implies use when appending memory, but provides no selection criteria, prerequisites, or exclusions.

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the 'Show' wording is consistent with them. The description does not add meaningful behavioral detail beyond those annotations, such as whether it reads from disk or whether it can affect the append log, but it also does not contradict them.

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 dense sentence that front-loads the verb and immediately lists the four kinds of information returned. There is no filler, repetition, or unnecessary explanation.

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?

The tool is relatively simple, has only one optional parameter and no output schema, and its safety profile is fully covered by annotations. However, the missing parameter semantics and the lack of guidance relative to memory_checkpoint make the description incomplete enough to be only minimally viable.

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?

The single parameter, project_root, has 0% schema description coverage, and the tool description never mentions it. Because the schema provides only a type with no explanation, the description should compensate but instead leaves the agent guessing how project_root affects the output.

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 uses a specific verb, 'Show', and enumerates precise resource categories: 'store paths, counts, current project identity, and append-log integrity.' This clearly differentiates it from mutating or memory-writing siblings like memory_forget and memory_ingest_project.

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 usage context is provided, and there is no statement about when to use this tool versus alternatives such as memory_checkpoint. The agent must infer entirely from the tool name that this is a read-only status/health inspection tool, so practical guidance is essentially absent.

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