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

With no annotations provided, the description carries the full burden. It conveys the core read-only behavior, but it does not mention the shape of the returned file list, recursion, error behavior for unknown projects, or any side effects. It is minimal but not contradictory.

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 or repetition. Every word adds meaning relative to the tool's 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?

This is a simple 1-parameter, read-only list operation with no output schema. The description accurately conveys the essential function and scope. It omits details like file-entry shape and recursive behavior, but these are minor gaps for a tool of this complexity.

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%, and the schema already describes the parameter as 'The name of the project.' The description adds essentially no new meaning about how 'projectName' is used or validated, so it stays at the baseline of 3.

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 the action clearly ('list all files'), the resource ('files'), and the scope ('within a specific project'). It is distinguishable from siblings: 'list_projects' enumerates projects, while 'memory_bank_*' operate on the memory bank.

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 explicit guidance about when to choose this tool over siblings such as 'list_projects' or 'memory_bank_read'. The context implies it is used to inspect files inside a known project, but the caveats and alternatives are not 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation through the word 'list', but doesn't disclose whether results are paginated, sorted, or complete; nor does it mention any potential side effects or limitations.

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 front-loads the action and resource. Every word is informative, and it is appropriately sized for a parameterless list operation.

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 simple parameterless list operation, this description covers the core usage. However, the complete lack of detail about the return format or any read behavior means an agent must rely on the server response to learn the output structure, and given the absence of annotations and output schema, slightly more context could be useful.

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 has zero parameters, so the description doesn't need to explain parameters. The schema confirms this, meeting the baseline for tools with no 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?

Description includes a specific verb ('list'), resource ('projects'), and scope ('in the memory bank'), making the purpose clear. It doesn't explicitly distinguish itself from siblings like list_project_files, but the target resource is different enough that an agent can infer the distinction.

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 about when to use this tool over alternatives. It only says 'List all projects in the memory bank' and gives no context about use cases, ordering, or relationship to memory_bank_read or list_project_files.

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 full burden of behavioral disclosure. It only repeats the action 'Read' without revealing any side effects, error handling, prerequisites, or return format. It offers no additional behavioral context beyond the tool's name.

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, efficient sentence that directly states the purpose without any waste. It is front-loaded and 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?

For a simple read tool with two parameters and no output schema, the description is minimal. It does not mention what the return value looks like, any potential errors (e.g., missing file or project), or any prerequisites. This leaves the agent without critical context needed to fully anticipate the tool's 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 description coverage is 100% with both parameters clearly named in the schema. The tool description adds no extra meaning about the parameters beyond the schema's basic descriptions. Baseline 3 is appropriate since the schema already covers parameter semantics.

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 verb ('Read') and a resource ('memory bank file') scoped to a project. It unambiguously distinguishes from siblings like list_projects, list_project_files, memory_bank_write, and memory_bank_update, which have different purposes.

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 reading file content, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. There is no guidance on when not to use it or when a sibling would be more appropriate, leaving usage to inference.

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 only says 'Update', which indicates a mutation, but does not state whether the update fully replaces the file content, what happens if the file does not exist (error vs. create), or any side effects. No permissions, reversibility, or error handling are mentioned. The description is too terse to give the agent confidence about the operation's behavior.

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, focused sentence with no filler or redundancy. It conveys the core purpose efficiently and is appropriately front-loaded with the verb and object. Nothing extraneous is present, and the length is appropriate for a simple 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?

Given that the tool is a mutation with no safety annotations and simple parameters, the description should clarify the prerequisite (file must exist) and the difference from memory_bank_write. It does not mention that the file must exist or that the operation might fail if it does not. While the schema covers parameters, the description leaves out important context about when and how to use this tool safely, making it incomplete for an agent to invoke correctly in all cases.

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 input schema already provides 100% coverage of all parameters with straightforward descriptions ('The content of the file', 'The name of the file', 'The name of the project'). The description adds no additional meaning or context about parameter usage, formatting, or dependencies. Since the schema does the heavy lifting, the baseline score of 3 is appropriate; the description adds no real enhancement.

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 ('Update') and the resource ('existing memory bank file for a specific project'). It distinguishes itself from siblings through the word 'existing', implying it modifies files that already exist rather than creating new ones. However, it does not explicitly name the alternative tool (memory_bank_write) or explain the difference explicitly, so it is clear but not fully differentiated.

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 implies that the file must already exist (via the word 'existing'), but it does not say 'use this for updates only, use memory_bank_write for new files'. An agent is left to infer the usage context from the sibling tool names. This is minimal guidance.

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 must disclose behavioral traits. It only says 'create', with no mention of whether an existing file would be overwritten, permissions needed, or error scenarios. It does not say what happens if the project doesn't exist or if there are constraints. This is a significant gap for a write operation.

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 with no fluff. It is front-loaded with the primary action and resource. It earns a high conciseness score, though it could have been slightly more informative without becoming verbose.

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 3-parameter write tool with no output schema, the description is minimal but somewhat sufficient given the schema covers all params. However, it lacks details about failure modes, idempotency, or how it relates to sibling tools. An agent might need more context to handle edge cases correctly.

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%, with each parameter having a basic description ('The content of the file', etc.). However, the tool description adds no additional meaning beyond what the schema already states. Baseline is 3 because the schema does the heavy lifting; the description does not enhance parameter understanding.

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 ('Create') and resource ('a new memory bank file'), and specifies it's for a specific project. It distinguishes from siblings like memory_bank_update by using 'new', though it doesn't explicitly name alternatives. This is clear but lacks explicit 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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention that it's for creating new files only, nor does it reference update/read tools. An agent must infer usage from the name and description alone.

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