nexo_lifecycle_wait_for_stop

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

No annotations provided, so description bears full responsibility for behavioral disclosure. It implies polling/blocking but doesn't specify if it's synchronous, how it handles timeout, or what happens if session never stops. No mention of side effects or safety.

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?

One sentence, very concise, but sacrifices necessary detail. It is front-loaded but under-specified. Conciseness at cost of completeness.

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?

With no output schema and no parameter explanations, the description is insufficient for a blocking lifecycle tool. Missing details on return value, error behavior, and parameter roles.

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?

Input schema has 3 parameters with 0% description coverage. The description does not explain any parameter (event_id, timeout_ms, poll_ms). It fails to add meaning beyond the schema's names.

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 it waits for a NEXO session to become inactive for a canonical lifecycle event. It distinguishes from sibling tools like nexo_lifecycle_wait_for_diary (waits for diary) and nexo_lifecycle_stop_nexo_session (actively stops session). However, it could be more precise about what 'no longer active' means.

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 explicit guidance on when to use this tool versus alternatives (e.g., wait_for_diary, stop_nexo_session). The description only states what it does, not context or conditions for use.

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