nexo_memory_answer

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

With no annotations, the description only discloses that answers are given only when evidence exists, but it does not specify what happens otherwise (e.g., empty result, error), nor any other behavioral traits like side effects or permissions.

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 short sentence, but it is under-specified and does not earn its place by providing sufficient value. It sacrifices completeness for brevity.

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 complexity (4 undisclosed parameters, no output schema, many siblings), the description is severely incomplete. It fails to explain inputs, outputs, or the critical condition 'only when evidence exists'.

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 4 parameters with 0% description coverage. The description adds no information about their meaning, so the agent has no guidance on how to fill 'query', 'project_hint', 'time_range', or 'limit'.

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 'Answer a memory question only when evidence exists,' which gives a verb and resource, but 'memory question' is vague and does not differentiate from siblings like 'nexo_memory_search' or 'nexo_answer'.

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 is provided on when to use this tool versus alternatives (e.g., 'nexo_memory_search' for searching without answering, or 'nexo_answer' for general answering). The condition 'only when evidence exists' hints at usage but is insufficient.

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