nexo_auto_flush_stats

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

With no annotations, the description carries the full burden. It only states what the tool provides (stats) without disclosing any behavioral traits such as side effects, read-only nature, permissions, or rate limits. The description is insufficient for an agent to understand the operational impact.

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 extremely short, but it is not concise—it is under-specified. An effective description should add value beyond the name; this one barely does, and it lacks structure or any helpful details.

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 no output schema, no annotations, and a single parameter, the description should explain what the stats contain and how the parameter influences results. It provides none of that, making it severely incomplete for an agent to use correctly.

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?

Schema description coverage is 0%, and the description does not mention the single parameter 'days' at all. It fails to explain its meaning, range, or effect on the output, leaving the agent to guess based on the schema defaults.

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 states it provides stats for pre-compaction auto-flush activity, which indicates the tool returns statistical data. However, it lacks an action verb like 'Retrieve' or 'Get', making the purpose somewhat vague. It does distinguish from sibling nexo_auto_flush_recent by focusing on stats rather than recent events, but this differentiation is implicit.

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 (e.g., nexo_auto_flush_recent). There is no mention of context, prerequisites, or when-not to use it. The agent must infer from the name and description alone.

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