nexo_ask

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

Description adds the asynchronous delivery detail ('on next heartbeat') beyond the schema. However, it omits other behavioral traits such as whether a response is expected or if there are any restrictions. With no annotations, the burden is moderate, but the description partially fulfills it.

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 no filler. It communicates the essential purpose concisely. Could be slightly more structured but earns its place.

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?

For a simple three-parameter tool with no output schema, the description sufficiently covers the purpose and delivery timing. Some users might want more details on what happens after the question is asked, but it's reasonably complete.

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 100%—all three parameters have descriptions. The tool description does not add any meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 the action (ask a question), the resource (another session), and the timing (next heartbeat). It distinguishes from sibling tools like nexo_answer and nexo_send.

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?

Description implies usage for inter-session questions but provides no when-to-use or when-not-to-use guidance. No mention of alternatives or exclusions.

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