nexo_ask

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

Mentions timing behavior ('next heartbeat') but lacks details on persistence, limits, or whether the target must be active. With no annotations, more behavioral context would help.

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 that is front-loaded and efficient, with no extraneous information.

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 tool with 3 string params and no output schema, the description covers the core purpose and a key behavioral trait. Minor gaps like return value or errors are acceptable.

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 covers all 3 parameters with descriptions. The description (e.g., 'Your session ID') adds minimal value beyond the schema, so 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 to another session' and specifies the timing ('on next heartbeat'), distinguishing it from siblings like nexo_send 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?

Implies use for asynchronous inter-session communication but gives no explicit when-to-use or alternatives. Among many sibling tools, an agent might need more guidance to choose correctly.

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