bookshelf_download_clients

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

The description explicitly labels operations with 'WRITE: this modifies your Bookshelf instance' or 'DESTRUCTIVE: this deletes data', which provides important behavioral cues. Since no annotations are provided, the description carries the burden of disclosing mutating vs read-only behavior, and it does so effectively. It also notes query parameters like `forceSave` and `forceTest`, which adds transparency about optional behaviors.

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 well-structured as a bulleted list of operations, which improves scannability. However, it is quite long (16 operations) and redundant, repeating 'WRITE: this modifies your Bookshelf instance' for every write operation. Each operation line is terse, but the overall length could be trimmed by grouping similar operations or noting the write/destructive flag once. It earns a middle score for being organized but not optimally 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?

Given the tool's complexity (16 operations, two main resource types), the description provides a comprehensive enumeration of all operations with signatures and safety flags. It also names the query parameters for each operation. However, it lacks details about return values (though an output schema exists) and does not explain the `arguments` dict structure for each operation, which is a notable gap. Overall, it is fairly complete for a facade tool.

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 provides an `operation` enum and an `arguments` object, but the description does not explain the structure or required keys for `arguments`. With 0% schema description coverage, the description fails to compensate by detailing parameter meanings. It lists operation signatures like `bookshelf_create_downloadclient(force_save=False, body={})`, which hints at parameters, but it does not explain what `body` should contain or what `forceSave` does beyond a name. This is a significant gap for a tool with 2 parameters and nested objects.

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 lists all operations with a specific verb and resource (e.g., 'Create downloadclient action', 'Bulk delete downloadclient bulk', 'Fetch a single downloadclient by id'). It distinguishes between downloadclient and remotepathmapping operations, which helps differentiate from siblings like bookshelf_indexers or bookshelf_storage. However, it is not a single-purpose tool but a facade for many operations, which slightly reduces clarity.

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 explicitly says to pass `operation` and an `arguments` dict, which is a clear usage instruction. However, it does not provide guidance on when to choose one operation over another or when to use this tool versus sibling tools like bookshelf_indexers or bookshelf_storage. It also does not state any prerequisites or exclusions, so the usage guidance is minimal beyond the basic mechanics.

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