openl Export Trace

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

Description states clearing trace from memory with release:true, which implies mutation, contradicting annotations readOnlyHint=true. This is a serious inconsistency.

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 short sentences, no filler, front-loaded with key action. Each sentence adds value.

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?

No output schema, description says 'Returns full trace content' which is minimal but acceptable for simple export. However, the annotation contradiction and lack of alternatives guidance reduce completeness for effective use.

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?

Description adds meaning for 'release' parameter beyond schema (clearing trace). Schema itself has good coverage (75%), so baseline 3 is appropriate. No additional info for other parameters.

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?

Describes specific action 'Export trace as plain text' with clear resource 'trace'. Distinguishes from siblings by mentioning full trace content, but no explicit differentiation among many trace-related siblings.

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?

Provides guidance on using 'release' parameter but lacks context on when to choose this tool over sibling trace tools like openl_get_trace_nodes or openl_get_trace_node_details.

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