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

With no annotations, the description carries the full behavioral burden, but it only says what is fetched. It does not disclose read-only behavior, permission requirements, partial-failure handling, result ordering, or limits on the number of targets, all of which matter for a batch fetch.

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 wasted words. It immediately identifies the action, result, and batch scope.

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?

An output schema exists, so return values need not be explained. Still, for an unannotated batch tool with one loosely documented parameter, the description should clarify target format, batch constraints, and failure behavior; those gaps keep it at minimum viability.

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. It adds meaning by clarifying that targets represent multiple folders and files, but it does not specify the expected string format, whether paths or IDs are accepted, or any size limits for the array.

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 ('Fetch') and resource ('High-Density Identity Cards') and clarifies that it handles multiple folders and files in one call. It is clear enough to distinguish this batch-inspection tool from single-target siblings, though it does not explicitly name those siblings.

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 phrase 'for multiple folders and files in a single call (Multi-Query)' implies this tool is for batched lookups rather than single-target calls. However, there is no explicit guidance about when to prefer this over individual inspection tools or when not to use it.

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, the description carries the full burden for a write tool and omits the core behaviors: what merge_mode actually does, whether existing knowledge is overwritten or appended, idempotency, and what happens when entity_path does not resolve. It does disclose the output-formatting convention (high-density English for specs, Indonesian slang for aliases), which is real value, but write semantics remain undisclosed.

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?

Front-loaded with the action, then the two formatting mandates, with no filler sentences. Slightly repetitive in the doubled 'MANDATORY:' prefix, but efficient overall.

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 12-parameter mutation tool with zero schema coverage and no annotations, the definition is under-specified: merge semantics, the required path's expected form, and symbol scoping are all absent. The output schema removes the need to explain return values, but that alone does not close the gap.

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 0%, so the description must compensate. It names eight of twelve parameters (purpose, logic_phases, upstream, downstream, guardrails, side_effects, error_handling, colloquial_aliases) and gives a content convention for two of them, but never explains entity_path, symbol_name, merge_mode, or child_summary — including the only required parameter.

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?

States a specific verb ('Save deep understanding') and resource ('a file/folder or function/symbol'), which is enough to separate it from the read-oriented siblings (inspect, find_by_intent, get_phase_map). It stops short of naming the write counterpart (memory_sync_codebase), so the boundary with auto-generation is not drawn.

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 spends its words on mandatory content formatting, not on when to call this versus memory_sync_codebase or the inspection tools. There is no stated trigger, no prerequisite (e.g. entity must exist in the index), and no exclusion criteria.

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, the description carries the behavioral burden. It implies a non-mutating search and clarifies accepted query styles, but it does not discuss matching behavior, result limits, permissions, or other operational traits.

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. The core action and the accepted query styles are stated efficiently.

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 simple, has one required parameter, and includes an output schema, so the description need not explain return values. It conveys enough to attempt a call, though it lacks explicit guidance on when to choose this tool over the siblings.

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 single 'terms' parameter. It usefully explains that terms may be natural language, slang, command habits, or typos, but it does not clarify how the array is interpreted or whether multiple terms affect matching.

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, 'Search', and specific resource types: symbols, files, and exact code blocks. It is clear what the tool does, though it does not explicitly differentiate itself from the sibling memory_* 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?

The description implies usage by listing input styles such as natural language, Indonesian slang, command habits, and typos. However, it does not state when to use this tool versus alternatives or when not to use it.

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, the description has to carry behavioral disclosure. It makes clear this is a read-style retrieval of a derived phase map rather than raw code, but it does not cover freshness, supported script types, failure behavior, or whether analysis has side effects.

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 phrase contributes: the action, the resource, the scope, and the reason to prefer this over reading raw code.

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?

An output schema exists, so return-value details need not be repeated. For a one-parameter tool this is close to sufficient, but the lack of annotations and parameter documentation leaves gaps around supported inputs and behavioral expectations.

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 lone file_path parameter. It only implies that the path refers to a script; it does not clarify format, relative vs absolute paths, supported extensions, or what happens if the file cannot be analyzed.

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 ("Retrieve") and a specific resource ("detailed internal logic execution phase map for a script"), and it clarifies the value by saying this is done "without reading raw code." It is distinguishable from most sibling tools, though it does not explicitly name alternatives.

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?

Usage is implied: call this when you need to understand a script's execution phases without inspecting raw source. There is no explicit when-not guidance, prerequisites, or comparison to sibling tools such as memory_find_by_intent or memory_batch_inspect.

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. It usefully discloses how change detection works (AST + hashing) and what it produces (exact line and symbol deltas), but 'sync' implies writes into the memory store and the description never says what gets mutated, whether it is idempotent, or what it costs on a large codebase.

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?

One sentence, front-loaded with the verb and mechanism, with no filler. Every clause (AST parsing, SHA-256, line and symbol changes) contributes distinct 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?

An output schema exists so return values are covered, and the zero-parameter surface is simple. However, with no annotations and an implied mutation, the description omits side effects, scope of the sync, and failure/cost behavior, leaving the agent short of what it needs for a write-shaped tool.

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 tool takes zero parameters, so the baseline is 4. Nothing about inputs needs explaining, and the description correctly spends no words on them.

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?

States a specific verb and resource ('sync codebase') and adds the mechanism (AST parsing, SHA-256 hashing) plus the outcome (detect line and symbol changes). It is clear what the tool does, but it never names or contrasts itself with the memory_* siblings, so an agent still has to infer the boundary.

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 statement of when this should be invoked versus the sibling inspection/query tools, no prerequisites, and no exclusions. The word 'Automatically' even leaves ambiguous whether the agent should call it at all or whether it is triggered internally.

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