workspace_export_paper_reading_report

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

No annotations are provided, so the description carries full behavioral burden. 'Deterministic' is a useful trait (stable output), but it says nothing about whether this is read-only, whether it writes a file, permission requirements, or how the report is delivered.

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 almost terse to the point of under-specifying for a two-parameter export tool.

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 annotations, no output schema, 0% param coverage, and a non-obvious 'max_candidates' parameter left unexplained. The description does not supply enough context for an agent to invoke this confidently.

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 neither parameter is explained. 'max_candidates' (default 5) is particularly opaque for a report on 'one stored paper' and the description does nothing to clarify it or the paper_id semantics.

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 ('Export') and resource ('deterministic Markdown reading report') scoped to 'one stored paper'. It is distinguishable from export siblings like workspace_export_reading_bundle, but it never explicitly contrasts itself with those 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?

The phrase 'for one stored paper' weakly implies the paper must already be in the workspace, but there is no explicit when-to-use, when-not-to-use, or alternative routing among the several other export tools.

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