memoryos_list_support_customers

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

The description only says 'List' which implies a read-only operation, but it does not disclose any side effects, pagination behavior, or whether the tool returns partial or full summaries. With no annotations, more behavioral detail is expected.

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, focused sentence with no unnecessary words. It is appropriately short for a straightforward list operation.

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?

The description is minimal and does not explain what a 'customer summary' contains, how results are ordered, or what the output looks like. Since there is no output schema, this missing context leaves the tool incomplete for an agent.

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?

The input schema fully describes the parameters and their types/defaults, but the description adds no semantic explanation of 'limit' or 'cursor'. Since schema coverage is high, a baseline score of 3 is appropriate.

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 action ('List') and the resource ('Customer Support schema customer summaries'), distinguishing it from generic list_memories. However, the phrase 'Customer Support schema customer summaries' is slightly awkward and could be more explicit.

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 is given on when to use this tool versus alternatives such as memoryos_list_memories or memoryos_get_support_stats. The description does not explain the intended use case or provide any exclusions.

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