nexo_local_context

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

No annotations provided, so the description carries the full burden. It discloses that the tool retrieves local evidence (a read operation) and provides mode-specific behavior. It does not mention side effects or permissions, but the core behavior is clear.

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?

Two sentences that are well-structured and front-loaded: the first sentence states the purpose, and the second provides usage guidance. No unnecessary words.

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?

With 9 parameters, no output schema, and many sibling tools, the description is insufficient. It lacks explanations for most parameters, the nature of 'evidence', and how to effectively use the tool. An agent would struggle to use it correctly without additional context.

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?

Input schema has 9 parameters with 0% coverage, and the description only adds value for 'mode' and hints about 'max_chars' and 'query' in full mode. It does not explain other important parameters like 'query', 'limit', 'evidence_required', 'current_context', etc.

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 'Retrieve local evidence before answering or acting,' providing a specific verb and resource. However, it does not differentiate from sibling tools like nexo_context_packet or nexo_context_router, which may have overlapping purposes.

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 explicit mode guidance: 'Use mode='compact' for normal answers. Use mode='full' only for deep debugging, ideally with a higher max_chars and a specific query.' It implies appropriate use cases but does not mention alternative tools or when not to use this tool.

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