list_entities

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

Discloses internal behavior (Qdrant Facet API with fallback) and implies read-only nature. Since no annotations exist, this adds valuable context beyond what structured fields provide.

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?

Two sentences, each earning its place: first states purpose, second adds technical transparency. No wasted words.

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?

Covers purpose and internal behavior succinctly. With an output schema present, return values need not be described. Slightly lacking on when to use versus siblings.

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?

Zero parameters with 100% schema description coverage (trivially). Description adds no parameter details but is unnecessary due to lack of parameters.

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 clearly states the verb 'List' and the resource 'which users/agents/runs currently hold memories'. It distinguishes from sibling tools like get_memories and search_memories by focusing on entities that hold 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?

Provides version-specific implementation details but no explicit guidance on when to use this tool versus alternatives like search_memories or mcp_get_entity. Usage context is implied but not stated.

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