Get memory bank

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

The readOnlyHint and openWorldHint annotations already establish the read-only, closed-world nature. The description adds useful behavioral detail beyond that: it loads ALL memories and supports exact or partial title matching, which affects how the agent should interpret results.

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 core operation is stated first, followed by a focused usage condition, making it easy for an agent to parse quickly.

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 tool with one parameter, read-only annotations, and an output schema, the description covers the main operational details: what to load and when to use it. The only notable gap is the ambiguity around partial matches resolving to multiple banks, given the claim that it loads from 'one bank.'

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?

With 0% schema description coverage, the description must compensate for bank_title. It states that the parameter is a title match with exact or partial matching, but it does not clarify behavior when a partial match returns multiple banks, case sensitivity, or formatting expectations.

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 and resource: 'Load all memories from one bank by title'. It clearly distinguishes itself from list_banks and get_memories_by_date_range through the title-based, bank-scoped behavior, though it does not explicitly contrast with search_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?

It gives an explicit trigger condition: 'USE when a bank title matches the topic or person the user is asking about.' This clarifies when to call the tool, but it does not state when not to use it or suggest alternatives such as search_memories.

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