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

With no annotations, the description carries the burden of exposing behavior. It discloses format/style constraints and the `include_references` condition, but does not mention whether the operation is read-only, what happens with an empty list, or any side effects. It adds some behavioral context but not comprehensive transparency.

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 three sentences, front-loaded with the primary purpose, and every sentence adds specific usage information. 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?

While the output schema exists and the core parameters are covered, the description does not explain what 'current reading list' means, nor does it address the `collection` and `engines` parameters. This leaves ambiguity for a tool with 5 optional parameters and no other annotation.

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%, so the description must compensate. It explains `format`, `style`, and `include_references` with valid values and conditional logic, adding real meaning. However, `collection` and `engines` are left entirely undocumented, leaving 2 of 5 parameters unexplained.

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 the tool exports the current reading list in multiple formats (citations, abstracts, BibTeX, full-text corpus), distinguishing it from siblings like saved_list or saved_add by the export action. It uses a specific verb and resource.

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 provides explicit valid values for `format` and `style`, and gives guidance for using `include_references` with `fulltext`. It does not explicitly name alternative tools, but the context of exporting the whole reading list versus per-article tools is implied.

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