export_session_data

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the optional file-path behavior, but it does not state whether the tool returns JSON when no path is given, writes a file when a path is supplied, or what happens for invalid or missing sessions. This is a significant transparency gap for a tool with no annotation safety net.

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 sentence with no filler, and the core verb and resource are front-loaded. It is efficiently structured, though it sacrifices potentially useful guidance for brevity.

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 two-parameter export tool, the core contract—export the full session as JSON, optionally to a file—is minimally conveyed. However, without annotations or an output schema, return behavior, file-writing semantics, and error conditions remain ambiguous. It is adequate but not fully complete.

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 description coverage is 0%, so the description must compensate. It only clarifies 'output_path' as an optional file path; it does not explain 'session_id' beyond the property name. The property names are self-explanatory, but the description adds little meaning beyond what the schema already shows, which is insufficient at 0% coverage.

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 names a specific operation ('Export'), a specific resource ('full session bundle'), and a format ('JSON'), which clearly communicates what the tool does. It is distinguishable from siblings like get_session_info in that it exposes the full bundle, but it does not explicitly name a sibling it is not, so it stops short of top-level differentiation.

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?

There is no guidance on when to use this tool versus alternatives such as get_session_info, list_artifacts, or complete_session. The phrase 'full session bundle' implies a broad export, but there are no explicit conditions, prerequisites, or exclusions, leaving the agent to infer when this tool is appropriate.

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