Session Trace Export

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

The annotation readOnlyHint=false is consistent with the description's claim that it saves an artifact. The description adds useful context (output is a local artifact, scope is limited to owned sessions), but omits whether this persists to a specific location, overwrites existing files, or requires write permissions.

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 no wasted words. Efficient, though arguably too terse to carry the required semantics for a tool with an undocumented parameter.

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?

An output schema exists, so return values need no explanation. As a one-parameter export tool the description is adequate at a minimum, but it leaves the parameter unexplained and gives no behavioral detail about where or how the artifact is saved.

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% and the single parameter session_id is never mentioned in the description. The phrase 'owned session trace' loosely implies a session identifier is required, but the description does not compensate for the undocumented parameter, which is especially weak given its low 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?

States a specific verb and resource: saving a session trace as a local artifact. 'Owned' adds a scope qualifier. It is clear on its own but does not explicitly differentiate from sibling session tools like session_get or sessions_list.

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?

'For bounded inspection' hints at the intended use case, implying you export when you want to examine a trace offline. However, it never states when to use this over session_get or other session tools, nor any prerequisites or exclusions.

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