auto_context

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

There are no annotations, so the description carries the transparency burden. It usefully discloses that only top, high-importance, active memories are returned and that the output is XML. However, it does not state whether the tool has side effects, how 'active' is determined, or behavior when no memories match.

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 clear sentence with a useful label prefix. No filler words; the key behavior, filtering criteria, output format, and intended moment of use are all packed 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?

For a read-like boot tool with an output schema and all optional parameters, the description is workable but incomplete. The output schema covers returns, yet the project parameter and the meaning of 'active' are not explained, so an agent has to infer important semantics from parameter names.

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 does not mention limit, project, or min_importance. 'High-importance' and 'top' loosely map to min_importance and limit, but project is entirely unaddressed, so the description does not compensate for the lack of schema 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 distinct action ('Recalls top high-importance active memories') and a concrete output ('formatted in XML'), with a specific use case ('session initialization'). This distinguishes it from siblings like list_memories or search_memory by selection criteria and format, even though no sibling is named explicitly.

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 explicitly positions the tool as a boot/session-initialization tool, which tells the agent when to use it. It does not explicitly contrast it with alternatives or state when not to use it, so it stops short of a 5.

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