nexo_cognitive_stats

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

No annotations are present, so the description must fully disclose behavioral traits. It states that the tool returns metrics but does not clarify side effects, read-only nature, or authorization requirements. The description is insufficient for a tool with no annotation support.

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, front-loaded sentence with no redundant information. Every word contributes to understanding the tool's output, making it highly concise and well-structured.

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 covers the basic purpose but lacks details on output format, constraints, or performance implications. Given no output schema and no annotations, the description could be more complete by specifying the return structure (e.g., JSON fields). It is minimally adequate for a simple stats tool.

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?

There are no parameters, and the input schema is empty. The description adds value by specifying what metrics are returned (STM/LTM counts, strengths, etc.), which goes beyond the schema. With no parameters, the baseline is 4, and the description compensates well.

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 lists specific metrics (STM/LTM counts, strengths, retrieval stats, quarantine counts), clearly indicating the tool's purpose. However, it lacks an explicit action verb and does not differentiate from the sibling tool 'nexo_cognitive_metrics', which likely provides related information.

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 like 'nexo_cognitive_metrics' or 'nexo_cognitive_inspect'. The description does not mention any context or prerequisites for usage.

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