nexo_cognitive_control_observatory

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

The description indicates it is 'read-only', implying no side effects, but does not explain what the metrics represent, how they are computed, or any rate limits. With no annotations, this is insufficient for an agent to fully understand behavior.

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, which is concise but lacks structure. It front-loads the read-only nature but omits parameter details or output format, making it minimally adequate.

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 tool has one parameter with no explanation, no output schema, and the description only lists domains. An agent would lack critical information on how to invoke it correctly and what to expect in return.

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 'window_seconds' has no schema description (0% coverage) and is not mentioned in the tool description. Agents have no guidance on its purpose or valid values.

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 provides 'Read-only metrics' for specific domains (Local Context, learnings, followups, intraday memory), identifying the resource and action. However, it does not differentiate from siblings like nexo_local_context or nexo_intraday_memory_cycle.

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 gives no guidance on when to use this tool versus alternatives, such as nexo_local_context or nexo_memory_health. No exclusions or prerequisites are mentioned.

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