nexo_memory_search

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

No annotations provided. Description only mentions 'evidence-first results', implying sorting but no disclosure about side effects, permissions, or rate limits. Minimal behavioral insight beyond the obvious search action.

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?

Single sentence with key information (what it does and evidence ordering). No fluff, but could include more detail without becoming verbose. Good front-loading of purpose.

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 5 parameters, no output schema, and many siblings, description fails to cover return format, parameter constraints, or when to use. Incomplete for effective agent selection and invocation.

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 description coverage is 0%, placing burden on description to explain parameters. Description provides no explanation for 'depth', 'limit', 'time_range', or 'project_hint'. Agent cannot infer parameter semantics from this description.

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?

Description clearly states 'Search Memory Observations v2 with evidence-first results', specifying verb, resource, and result ordering. It differentiates from siblings like nexo_evidence_search and nexo_memory_observation_list by version and ordering, but could be more explicit about what v2 entails.

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 on when to use this tool over alternatives. With many sibling tools (e.g., nexo_evidence_search, nexo_memory_observation_list), the agent lacks context on when to prefer this one.

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