export_eval_cases

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

No annotations are provided. Description only says it exports session data, with no mention of side effects, auth, read-only nature, or how the export is delivered (file, response body). The absence of behavioral detail makes it hard for an agent to anticipate consequences.

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?

One sentence, no filler, verb-first with purpose embedded. 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?

With no output schema and no annotations, the description does not state what the export returns, whether it writes a file, or if it has side effects. For an export operation in a session-management tool, this is a significant gap for an agent to safely invoke it.

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 covers 'format' (jsonl or json) but not session_id. The description's 'session data' gives context for session_id but doesn't clarify format options or output details. Since coverage is exactly 50%, the description adds only marginal value.

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?

Clear verb+resource: 'Export session data as structured eval cases for model evaluation.' It specifies exactly what it does and distinguishes from sibling tools like get_session or get_session_events by the transformation into evaluation cases.

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?

Implied usage for model evaluation, but no explicit alternatives or when-not-to-use. Does not mention which sibling tools to prefer for plain session viewing.

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