nexo_session_export_bundle

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

With no annotations, the description must disclose behavioral traits. It only states the tool exports a bundle, omitting whether it is destructive, requires specific session state, has size limits, or what the output format is. Minimal transparency beyond the action.

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?

A single, front-loaded sentence with zero wasted words. Clearly states the purpose and use cases.

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 no output schema, no parameter descriptions, and many related sibling tools (e.g., nexo_continuity_resume_bundle, nexo_session_portable_context), the description is insufficient for an agent to correctly invoke the tool. It lacks parameter meaning and output format.

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 input schema has 0% description coverage, and the description does not explain the meaning or usage of either parameter (sid, path). Parameters have defaults but no semantics added.

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 specifies the action ('Export') and the resource ('machine-readable session bundle') with explicit use cases ('cross-client handoff or archival'). It distinguishes itself from sibling tools by emphasizing machine-readability and export functionality, e.g., vs. nexo_session_portable_context.

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., nexo_continuity_resume_bundle or nexo_session_portable_context). The phrase 'for cross-client handoff or archival' provides context but no when/when-not criteria.

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