nexo_lifecycle_event

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

No annotations provided. Description mentions 'durable' and a version-specific behavior, but lacks disclosure of side effects, permissions, or error scenarios for a write operation.

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?

Two focused sentences: first defines purpose with action list, second adds version context. Efficient and front-loaded.

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?

Missing output schema and no description of return values beyond a hinted plan. For a tool with 8 parameters and no output schema, more context on response or side effects would be needed.

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 already defines all 8 parameters with clear descriptions (100% coverage). Description adds the list of actions but does not significantly augment schema details; 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?

Clearly states the tool records durable lifecycle events and lists specific actions (close/delete/archive/switch/app-exit/window-close). Distinct from sibling tools like nexo_lifecycle_status or nexo_lifecycle_complete_canonical.

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 usage when a lifecycle event needs recording, but no explicit guidance on when not to use or how it compares to alternatives like nexo_lifecycle_stop_nexo_session.

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