bookshelf_list_command

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

The annotation readOnlyHint=true already indicates the operation is safe and read-only. The description adds no behavioral context beyond this: it doesn't state what the returned list contains, whether it includes all commands, or any limitations. It neither contradicts the annotation nor enhances transparency.

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 extremely brief, but this is under-specification rather than effective conciseness. Two words fail to convey the tool's purpose or scope. It is not front-loaded with useful information; it is simply incomplete.

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 and a read-only annotation, the description is profoundly inadequate. It does not explain what a 'command' is in this domain, what the list represents, or when to call this tool. The description provides almost no value toward understanding the tool's behavior or selection.

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 tool has zero parameters and the schema coverage is 100% (empty schema). The baseline for zero parameters is 4, and the description is not required to explain parameters. The description's silence on parameters is acceptable here.

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 'List command' is essentially a tautology that restates the tool name 'bookshelf_list_command'. It identifies the verb (list) and resource (command) but lacks any specification of what kind of commands are listed or how they might be filtered, making it unclear and not distinguishable from sibling list tools.

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 alternatives such as bookshelf_get_command, bookshelf_run_command, or other list_* tools. There is no mention of context, prerequisites, or exclusions.

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