bookshelf_system_commands

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

Some behavioral hints are embedded in the text, such as 'DESTRUCTIVE' for delete commands and 'WRITE' for modifications, which warn about side effects. However, many operations (e.g., get, list, ping) lack explicit notes on permissions, idempotency, or potential errors, and no annotations are provided to supplement.

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 structured as a clear bullet list of operations with brief, one-line descriptions, making it scannable. The repetition of the 'bookshelf_' prefix is slightly redundant but does not hinder readability. It is concise in phrasing, though the overall length is substantial due to the number of operations.

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 tool with many subcommands, the description is sparse. It lacks details on the arguments parameter, return formats, error scenarios, and relationship between operations. The output schema is not addressed in the description, and the brief descriptions only cover basic actions without sufficient context for correct usage.

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 'operation' parameter is partially explained through the enum list, but the 'arguments' parameter is not described at all. The schema provides no descriptions for arguments, and the description does not clarify its structure or how it varies per operation, leaving the parameter semantics ambiguous.

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 identifies the tool as handling 'bookshelf system commands' and enumerates specific operations (delete, get, list, etc.), making its general purpose evident. However, it does not explicitly state the overall scope or when the parent tool is the appropriate entry point compared to categories like media or config.

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 no guidance on when to use this tool versus sibling tools (e.g., media library, config). It lists operations but gives no context on selection criteria, prerequisites, or typical use cases, leaving the agent to infer from operation names alone.

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