aiworkhub_manager_ai_memory_related

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

readOnlyHint=true already tells the agent this is a safe read. The description adds the opaque claim of a 'bounded' lookup without stating the bound (limit, depth, or traversal distance) or whether a missing key errors or returns empty. With annotations carrying the safety profile, the remaining behavioral value is minimal.

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?

It is one short sentence with no filler, and the read-only scoping is front-loaded. However, the brevity tips into under-specification rather than tightness, so conciseness is achieved at the cost of substance.

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 shape need not be described. For a one-parameter lookup that is otherwise simple, the definition is barely adequate — an agent could call it but would not know how to form a valid key or interpret the 'bounded' result scope.

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% and the single required parameter 'key' is only given a title. The description neither explains that 'key' is a canonical AI Memory key nor whether it accepts an ID, path, or relationship handle — the description fails to compensate for the schema gap.

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 phrase 'related canonical AI Memory lookup' identifies the resource (AI Memory) and operation (related lookup), which is more than a restatement of the name. But 'bounded' and 'related' are left undefined, so an agent cannot tell precisely what this returns compared to sibling lookups like ai_memory_get or ai_memory_search.

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 on when to use this versus aiworkhub_manager_ai_memory_search, aiworkhub_manager_ai_memory_get, or the context_graph/kb_related siblings. The 'MANAGER READ' prefix signals a read class but not a selection condition.

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