nexo_memory_observation_stats

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

No annotations are provided, so the description must disclose behavioral traits. It only states it 'summarizes', implying a read-only operation, but does not confirm lack of side effects, required permissions, or rate limits. The description is too sparse to ensure safe invocation.

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 sentence with no fluff, achieving brevity. However, it omits critical details such as return format or parameter meaning, making it under-informative for its length. Conciseness should not come at the expense of completeness.

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?

Given the lack of annotations, output schema, and parameter descriptions, the description fails to provide sufficient context for an agent to understand the tool's purpose, inputs, and outputs. Critical gaps include what 'queue status' entails and the structure of the summary.

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 has 0% description coverage, and the description does not explain the 'days' parameter (integer, default 7). The agent must infer it represents the time range for summarization. The description adds no meaning beyond the schema field name.

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 ('Summarize') and the specific resources ('passive Memory Observations v2 rows' and 'queue status'). It distinguishes from siblings like nexo_memory_observation_list (which lists) and nexo_memory_health (which checks health). However, it could be more explicit about the 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?

No guidance on when to use this tool versus alternatives like nexo_memory_observation_list or nexo_memory_event_stats. There is no mention of prerequisites, suitable contexts, or exclusions. The agent lacks decision criteria.

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