nexus.context_retrieve

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

With no annotations, the description carries the full burden. It discloses that a single call returns multiple data types and gives specific behavioral guidance for the 'as_of' parameter, including the restriction against inferring time context from conversation. This adds valuable transparency beyond the schema.

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 concise: three sentences that convey the purpose, usage guideline, and a key behavioral note. Every sentence earns its place without redundancy.

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 existence of an output schema (not shown but indicated), the description appropriately avoids explaining return values. It covers the key combination of data types and the critical 'as_of' constraint. Minor gap: no mention of error conditions or performance, but overall sufficient for a retrieval 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?

Schema coverage is 50%, so the description should compensate. It adds meaningful detail for the 'as_of' parameter (e.g., max 90 days, no inference from context), but does not elaborate on user_id, query, or limit beyond what the schema provides. This meets the baseline but does not elevate.

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's purpose: retrieving context from prior sessions, conversations, or stored facts. It specifies that it returns 'memories, recent conversation turns, and knowledge entities together,' and distinguishes from sibling nexus.memory_search by stating 'Prefer this over nexus.memory_search when query is open-ended.'

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 a clear condition for use ('when user asks anything that might need context from prior sessions...') and suggests an alternative for more specific queries (nexus.memory_search). However, it does not explicitly list when not to use this tool or other exclusions.

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