create_library

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

No annotations are provided, so the description carries the burden. It discloses the admin authentication requirement, which is valuable. However, it does not describe side effects, reversibility, or any other behavioral traits beyond the obvious create action.

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 two sentences, front-loaded with the core action, and contains zero filler. It is appropriately concise.

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, the tool's input is entirely unexplained. Given that library creation is likely a complex operation with nested objects, the description is too sparse to serve as a standalone guide. The admin role inclusion helps, but key usage context is missing.

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 0% and the description adds no explanation of the 'library' parameter. The parameter is a free-form object with additionalProperties true, but the description does not indicate required fields (e.g., name, root), making it impossible to construct a valid request without external knowledge.

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 'Create a library' uses a specific verb and resource, clearly distinguishing it from siblings like update_library, delete_library, and list_libraries. The purpose is 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 states the authorization requirement ('Requires the Komga ADMIN role') but provides no guidance on when to use this tool versus alternatives. It does not mention relationship to scan_library, update_library, or any prerequisites beyond the role.

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