library_list

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

Annotations declare readOnlyHint, idempotentHint, destructiveHint, so the safety profile is covered. The description adds value by disclosing the default return behavior (previews vs full text), which annotations do not address. No contradictions.

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 clear sentence, efficiently conveying the main purpose and a key behavioral note. It is appropriately sized with no fluff.

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 an output schema exists for return values, the description focuses on the input behavior. However, it omits details about pagination (limit, offset) and store selection, which are important for a listing tool. Adequate but not fully comprehensive.

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 should compensate. It mentions the default behavior hinting at 'include_text', but does not explain any parameters beyond their names. Parameter names are somewhat self-explanatory, but no additional meaning is added.

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 ReadingItems from a configured store', specifying the verb and resource. It distinguishes from siblings like 'library_get' (single item) and 'library_search' (search) by focusing on listing all items.

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 notes that by default previews are returned, hinting at when to use 'include_text', but does not provide explicit guidance on when to choose this tool over alternatives like 'library_search' or when not to use it.

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