abs_libraries

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

Beyond the annotations, the description discloses the auth mechanism (Bearer from ABS_API_TOKEN), a hosting constraint (self-hosted only), the dual gate required for writes (confirm=true plus ABS_ALLOW_WRITES=true), the dry-run-by-default behavior when confirm is omitted, and that destructive/credential actions emit an extra preview warning. That is exactly the kind of operational context annotations cannot convey.

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 opening sentences are well front-loaded with the highest-value facts (auth, write gating, dry-run). However, the trailing list of 26 actions is a flat restatement of the enum already present in the schema, adding length without adding meaning.

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 six-parameter destructive dispatcher with nested objects and no output schema, the description covers auth, safety gates, preview behavior, and parameter discovery. The gap is that it gives no hint about per-action return shapes or which actions are reads versus writes, leaving the agent to call help per action.

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 100%, so the per-field documentation already does the heavy lifting. The description still adds value by explaining the help/target discovery loop and the confirm-omission dry-run semantics, though it says nothing about the body, query, or params shapes beyond what the schema already declares.

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 names the toolset (Audiobookshelf libraries), states it hosts 26 operations, and enumerates every action, so an agent knows the exact scope. It does not, however, distinguish this tool from siblings like abs_authors, abs_search, abs_series, or abs_stats, several of which appear to overlap with actions listed here (get_authors, get_search, get_series, get_stats).

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?

It gives strong procedural guidance for the call pattern: action help with target to discover per-action parameters, and a dry-run-then-confirm workflow for writes. But it never says when to choose this tool over the sibling tools that cover authors, search, series, and stats, which is the main routing decision an agent faces.

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