nexo_lifecycle_wait_for_diary

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

The description indicates a blocking wait operation but does not explain timeout behavior, error conditions, return values, or consequences of success/failure. With no annotations provided, these gaps leave the agent underinformed.

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 front-loaded sentence with no extraneous content, but it lacks necessary detail, making it more underspecified than concise.

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 tool's complexity (blocking with timeout/poll), no output schema, and no annotations, the description provides only the minimal purpose. It misses critical details like return values, error handling, and what constitutes 'concrete evidence'.

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 description adds no meaning to the three parameters (event_id, timeout_ms, poll_ms) documented in the schema. Since schema description coverage is 0%, the description should compensate but fails to do so.

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 the tool's action ('Wait'), resource ('session_diary evidence'), and context ('before Desktop stops the session'), distinguishing it from lifecycle siblings like nexo_lifecycle_wait_for_stop.

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?

The description implies a specific usage scenario ('before Desktop stops the session') but does not explicitly state when to use this tool over alternatives like nexo_lifecycle_wait_for_stop or nexo_lifecycle_complete_canonical.

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