memoryos_get_user_stats

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

The verb 'fetch' indicates a read-only operation, and the description mentions 'tenant-scoped' which hints at permission boundaries. However, it does not explicitly state that there are no side effects or required permissions, leaving some room for inference.

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 well-structured and easy to parse.

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?

For a simple fetch operation, the description is adequate but omits details about what specific stats are returned or any error conditions. It covers the essential purpose but lacks comprehensive context that could aid an agent in fully understanding the tool's output.

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 description clarifies that the 'external_user_id' parameter refers to 'one external user', providing meaning beyond the bare schema type. It does not elaborate on format or constraints, but the context is sufficient for a single parameter.

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 (fetch), the resource (tenant-scoped memory stats), and the target (one external user). It distinguishes from sibling tools like memoryos_get_support_stats or memoryos_get_global_agent by specifying memory stats and external user scope.

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?

The description implies when to use this tool (for memory stats of a specific external user) but does not explicitly contrast with alternatives like support stats or global agent stats. Usage guidance is inferred rather than stated.

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