nexo_memory_event_stats

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

The description lacks detail on behavioral aspects such as read-only nature, output format, or aggregation details. Without annotations, the description should convey that this tool is read-only and what 'summarize' means (e.g., count per day, total). It does not disclose any side effects or permissions needed.

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 extraneous words, but it sacrifices completeness for brevity. While concise, it omits critical information that would be necessary for effective tool selection and invocation.

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 existence of sibling tools with overlapping purposes and no output schema, the description is incomplete. It does not explain the return format, whether the output is aggregated per period or total, or how 'days' affects the summary. Additional details about data scope and output structure are needed.

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 sole parameter 'days' has no description in the input schema (0% coverage) and the tool description does not explain its purpose or expected values. The agent cannot infer that 'days' likely controls the time window for event counts without external knowledge.

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 tool summarizes raw Memory Observations v2 event counts. It identifies the verb (summarize) and resource (event counts), which distinguishes it from sibling tools like nexo_memory_event_list that list events rather than summarize counts. However, the 'v2' tag is unclear and could be confusing.

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 provided on when to use this tool versus alternatives such as nexo_memory_event_list or nexo_memory_observation_stats. There are no examples, prerequisites, or conditions that indicate when this tool is appropriate.

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