list_readlists

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

The annotation readOnlyHint=true already confirms the read-only nature. The description adds no behavioral traits beyond mentioning optional filters, which are already reflected in the schema. It does not disclose pagination or sorting behavior.

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 concise sentence of nine words. It front-loads the core action and includes the key optional filters without any 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?

For a simple list operation with an output schema and read-only annotation, the description covers the essential purpose and the most relevant filter options. However, it omits any guidance on sorting and pagination parameters, which may be non-obvious from the schema alone. This is 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?

The description only mentions 'search text' and 'library' as filters, covering two of the six parameters. No information is given about page, size, sort, or unpaged, leaving their semantics unexplained. The schema has no property descriptions, so this is insufficient compensation for the 0% schema description coverage.

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 readlists, using the specific verb 'List' and resource 'readlists'. It also notes optional filters, distinguishing it from singular 'get_readlist' and mutation siblings.

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 implies the tool is for listing readlists with optional filters, but it does not explicitly state when to choose this over alternatives like get_readlist or search_books. No exclusions or alternative tool names are provided.

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