get_readlist_books

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

The annotation readOnlyHint=true already establishes the read-only nature. The description adds no additional behavioral context such as pagination, error handling, or dependencies on Komga API semantics. It essentially restates the tool's purpose without disclosing any traits beyond the annotation, providing minimal transparency value.

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 with 9 words, front-loaded with the verb and object. It is concise, focused, and avoids any fluff or repetition, making it an excellent example of brevity.

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 and a read-only annotation, the description is too sparse for a tool with 11 parameters. It omits the required readlist_id, pagination behavior, and filter semantics, leaving the agent to infer critical details from parameter names alone. This is insufficient for reliable tool invocation.

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?

With 11 parameters and 0% schema description coverage, the description must compensate for the lack of parameter documentation. It only says 'using Komga's filter query params', which is vague and does not explain any specific parameter, the required readlist_id, pagination defaults, or allowed filter values. This fails to provide meaningful semantics beyond the parameter names in the schema.

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 books in a readlist', specifying both the action (list) and the resource (books within a readlist). This distinguishes it from sibling tools like get_readlist (which retrieves readlist metadata) and list_readlists (which lists readlists). The mention of Komga's filter query params further clarifies its filtering capability, making the purpose unambiguous.

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 clear context about when to use this tool: when you need to list books inside a specific readlist, as opposed to general book search (search_books). However, it does not explicitly mention alternatives or when-not-to-use, stopping short of the highest transparent guidance.

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