list_libraries

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

The annotation readOnlyHint=true already signals a safe read operation. The description adds behavioral context by specifying that only libraries visible to the authenticated user are returned, which is relevant for access control and matches the 'authenticated user' requirement. No contradictions with annotations.

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 one short sentence, front-loaded with the verb 'List'. It contains only the essential information and no redundancy.

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?

This is a simple list operation with no parameters and an output schema available. The description sufficiently explains the tool's scope and purpose; no additional details (e.g., pagination or return format) are needed because no params exist and output schema covers return values.

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 input schema defines no parameters (100% schema coverage), and the description correctly provides no parameter details. The zero-parameter baseline is 4.

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 uses the specific verb 'List' with the resource 'libraries' and clarifies scope with 'visible to the authenticated Komga user'. This distinguishes it from sibling tools like get_library (which retrieves a specific library) and create_library/update_library/delete_library (which mutate).

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 does not explicitly mention alternatives or when-not to use this tool. However, the verb 'List' and the resource 'libraries' imply its use for enumerating libraries, which is distinct from get_library or scan_library. The visibility scope provides some context, but no explicit guidance is given.

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