saved_list

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

With no annotations, the description has full burden. It only states the tool lists items and a parameter flag, but does not disclose idempotency, read-only nature, pagination behavior, or any side effects.

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 sentence, concise and front-loaded with the core purpose. However, it may be too terse to be fully helpful.

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?

Despite having an output schema (unseen), the description fails to cover pagination, cursor semantics, or limit behavior. The tool has 3 parameters but only one is addressed, leaving gaps for a listing operation.

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%, yet the description only explains the 'detailed' parameter. Cursor and limit, which control pagination, are not described, leaving their meaning unclear beyond schema types.

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 'List saved-for-later items', which is a specific verb+resource. It distinguishes from sibling tools like saved_add and saved_delete, but not from other list tools; however, the name provides 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 only suggests setting detailed=True for full response, but provides no guidance on when to use this tool versus alternatives or when not to use it. Usage context is missing.

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