eval_export_reading_sessions

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

No annotations provided, so description carries full burden. It mentions exporting events and omitting file paths, but does not disclose side effects, state changes, or performance implications. Minimal behavioral context beyond basic operation.

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 sentences, no redundant information. Front-loaded with the core action and parameter. Every 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?

Given simple export tool with output schema present, description covers main purpose and root behavior. Could mention limit or output format, but output schema handles return. Mostly 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?

The description explains the 'root' parameter's default and behavior, adding value beyond the schema (which has 0% coverage). However, the 'limit' parameter is not mentioned, leaving its purpose unclear. Adds some meaning but incomplete.

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 uses a specific verb 'Export' and resource 'opt-in reading-session capture events' and distinguishes from sibling like eval_replay_reading_sessions by mentioning 'export' vs 'replay'. It also clarifies scope with 'selected root sidecar'.

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?

Clearly states when to use: 'to inspect real MCP reading calls and retrieval evidence without exposing file paths'. Provides context on default root behavior. Lacks explicit exclusions or alternatives but is sufficient for basic usage.

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