nexo_hot_context_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates the items are 'currently alive' (temporary) but does not specify side effects, read-only nature, or permissions. This is insufficient for 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 10-word sentence, which is concise but too brief to provide necessary context. It sacrifices clarity for brevity, earning a middle score.

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 tool's complexity (3 parameters, no output schema, many siblings), the description is incomplete. It fails to define key terms like 'hot-context items' or 'continuity window', and does not cover return values or filter behavior, leaving substantial gaps for an AI agent.

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 3 parameters with 0% description coverage, and the description adds no explanations. The agent has no guidance on the meaning of 'state' or the role of 'hours' and 'limit' beyond their names and defaults. This makes correct parameter usage unlikely.

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 the tool lists 'hot-context items' that are 'alive in the recent continuity window', providing a specific verb and resource. However, it does not differentiate from similar sibling tools like nexo_recent_context or nexo_context_router, leaving ambiguity about when to use this specific tool.

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 provides no guidance on when to use this tool versus alternatives. Given numerous sibling tools for context retrieval (e.g., nexo_recent_context, nexo_context_packet), the absence of usage context or exclusions significantly hinders correct selection.

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