bookshelf_run_command

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

The annotations already indicate readOnly=false and destructiveHint=false, but the description adds the explicit behavioral context 'WRITE: this modifies your Bookshelf instance.' This goes beyond the annotations by stating the side effect. It doesn't detail per-command effects, but the examples convey the range of consequences.

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 purpose and examples, followed by a succinct warning. Every word earns its place, with no fluff or repetition of schema information.

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 there is an output schema, return values are likely covered. The description provides enough context for an agent to understand the tool's purpose and how to construct the request, though it doesn't exhaustively list all commands or discuss asynchronous behavior. However, for a generic command runner, this is reasonably complete.

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 schema has one parameter 'body' with no description and no constraints (additionalProperties true), so schema description coverage is 0%. The description compensates by specifying that body is a CommandResource with a 'name' field and providing a list of valid names. This is essential guidance that the schema completely lacks.

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 states the verb 'Run' and the resource 'Bookshelf command', with a list of concrete examples (RefreshAuthor, AuthorSearch, etc.). It unambiguously differentiates from sibling tools like list/get/delete by focusing on execution.

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 clear context by saying this modifies the instance, implying it should be used when you want to trigger a command rather than inspect command metadata. However, it doesn't explicitly name alternative tools (e.g., bookshelf_list_command) or state when not to use it, so it falls short of a full 5.

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