workspace_export_reading_session_summary

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It mentions the output is 'deterministic', which is a useful trait, but does not disclose side effects, format, export destination, or any operational behavior. This is insufficient for a tool with no structured annotation support.

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, tightly-worded sentence that front-loads the core verb and object. Every word adds meaning, and there is no fluff or repetition.

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, no annotations, and only a one-sentence description, the tool is under-specified. The exact content of a 'deterministic recovery summary', the output format, whether it creates files or returns text, and error behavior are all unknown, leaving an agent with insufficient context to invoke it reliably.

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 description does not mention session_id at all. While the parameter name is reasonably self-explanatory, the description provides no elaboration on what constitutes a valid session identifier or how it affects the summary, so it fails to compensate for the missing schema documentation.

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 clearly states a specific action ('Export') and resource ('a reading session summary'), and adds the meaningful qualifier 'deterministic recovery summary'. It is not tautological and gives a reasonable sense of what the tool produces, though it does not explicitly distinguish itself from sibling export tools like workspace_export_reading_bundle or workspace_export_result_reading_context.

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?

The description offers no guidance on when to use this tool versus its siblings, no alternative names, and no exclusions. The phrase 'recovery summary' hints at a use case, but an agent has no explicit criteria for choosing this over the other export-related workspace tools.

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