saved_list

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

With no annotations provided, the description must disclose all behavioral traits. It only mentions that the tool lists items and that 'detailed' affects response fullness. It fails to disclose pagination behavior (cursor parameter), scope (user-specific vs global), or read-only nature. The description adds minimal value beyond the schema descriptions.

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 extremely concise (two sentences) and front-loaded with the core purpose. Every word serves a purpose, with no redundancy or filler.

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?

Given that an output schema exists (though not shown), the description does not need to explain return values. However, it could mention pagination or default behavior for a complete picture. The description is adequate for a simple list tool but lacks depth about scope and output structure beyond the 'detailed' flag.

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 coverage is 100%, so baseline is 3. The description's mention of 'detailed=True' adds a vague phrase 'full response' but does not clarify the exact format difference. It ignores 'limit' and 'cursor', which are already described in the schema. The description does not significantly enhance understanding of the parameters.

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 verb 'List' and the resource 'saved-for-later items', making the tool's purpose immediately clear. However, it does not specify the scope (e.g., current user's items), which could be inferred but not explicit. This distinguishes it from sibling tools like saved_add and saved_delete, but not from other listing tools that might have similar 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 provides one usage hint ('Set detailed=True for full response'), but no guidance on when to use this tool versus alternatives like messages_list or conversations_history. There is no mention of prerequisites, exclusions, or context-specific scenarios, leaving the agent without clear decision criteria.

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