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

With no annotations provided, the description carries the burden of behavioral disclosure. It notes the list is 'in-memory' and 'currently saved', indicating an ephemeral, read-only state, but it does not explicitly state that the tool causes no side effects or that it does not modify the list.

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 two sentences, front-loaded with the core action, and contains no redundant information. Every word 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?

The tool is simple with one optional parameter and an output schema, so return structure is covered elsewhere. However, the description fails to compensate for the missing parameter semantics and does not fully articulate the read-only nature, leaving gaps for an agent to infer.

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 schema has one parameter 'collection' with 0% schema description coverage, and the description does not explicitly explain this parameter. It only mentions a 'named' list, which hints at the connection but does not clarify that 'collection' is the list name, its valid values, or its default behavior.

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 lists papers saved in a named reading list with the verb 'List' and resource 'papers currently saved in a named in-memory reading list'. It distinguishes from siblings like saved_add, saved_remove, and saved_export by focusing on inspection/listing.

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 gives explicit context for use: 'Use this to inspect the working set before exporting or removing items.' This tells the agent when to invoke it, though it lacks direct exclusions or mentions of alternative tools.

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