aiworkhub_manager_ai_memory_get

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

The readOnlyHint annotation already declares the safety profile, so the description's burden is lighter. It does add meaningful scope ('active canonical') implying non-canonical or retired entries will not be returned, but it says nothing about miss behavior when the key is absent.

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?

A single front-loaded phrase with no filler; the 'MANAGER READ:' prefix signals role and safety at a glance. Slightly terse for the amount of behavior it leaves unstated, but nothing is wasted.

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 explanation is not required, and one-parameter scope keeps things simple. Still missing key format guidance and not-found behavior, both of which matter for a canonical-retrieval 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?

Schema description coverage is 0% for the single 'key' parameter, so the description must compensate and largely does not. 'exact' hints that the key is a literal match rather than a pattern, but no key format, namespace, or example is given.

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 operation on a specific resource: an exact-key lookup of an 'active canonical AI Memory' entry. The word 'exact' distinguishes it from the sibling search/related tools by implication, though it never names them 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?

'exact ... lookup' implies the caller must already know the key and should use the search sibling otherwise, but this is left to inference. There is no explicit when-to-use, when-not-to-use, or named alternative despite three AI Memory siblings existing.

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