list_library

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

Declares 'Read-only,' which is valuable but no other behavioral traits (e.g., pagination, rate limits) are disclosed. With no annotations, the description could add more, but the schema covers parameters well.

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?

Three crisp sentences: purpose, usage, and auth requirement. No fluff; front-loaded with core action.

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?

For a simple list tool with no output schema, the description covers scope, ordering, usage, and auth. Lacks error or result details but is sufficiently complete for decision-making.

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 parameters are fully documented there. The description adds no extra parameter details beyond confirming the default ordering 'newest first,' which is not a parameter.

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 action ('List'), resource ('saved papers'), scope ('authenticated user's library'), and ordering ('newest first'). It is distinct from sibling tools like 'search_papers' and 'save_paper'.

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?

Provides explicit context: 'Use this to review a reading list or to see what's already saved before saving more.' Also notes prerequisite 'Requires SF_API_KEY.' No explicit when-not-to-use, but enough guidance for typical scenarios.

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