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

With no annotations the description carries the full behavioral burden, and it discloses almost nothing: no mention that it is a read-only operation, no auth/permission requirements for 'shared' memories, no result limits, ranking or pagination behavior. 'Shared memories within one project' hints at scope but not at 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?

A single efficient, front-loaded sentence with zero filler. It is appropriately structured, though it is short to the point of under-specification rather than being padded.

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?

Three parameters at 0% schema coverage, no annotations, and no output schema, yet the description says nothing about return values, result shape, ranking or limits. For a search tool this leaves an agent guessing about both inputs and outputs.

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%, so the description must compensate and it largely does not. 'Within one project' maps to the required `project` param and 'search' weakly implies `query`, but the `type` parameter and all value formats, enums or matching semantics are entirely undocumented.

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 verb (search) and resource (shared memories), plus a scoping constraint (within one project). It is distinguishable from memory_write/memory_retract/memory_get by the verb alone, though it never explicitly contrasts itself with memory_brief or memory_get.

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 when-to-use guidance, no exclusions, and no reference to any of the five sibling tools. An agent must infer from the name alone whether this or memory_get / memory_brief is the right call.

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