List BookStack items

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that listing returns existence-style results rather than contents and hints at sort behavior, but says nothing about pagination (count/offset) or return shape, which matters for a 6-param list tool.

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?

Three tight sentences, front-loaded with the resource scope, then usage, then the alternative. No filler or repetition.

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 a read-only list tool with no output schema and 6 parameters, the description adequately covers purpose, use cases, and the get-vs-list distinction. Its only real gap is pagination/return behavior, which is a minor omission for a listing endpoint.

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 50%, so the description must carry some weight: it enumerates the type enum values inline and demonstrates the sort parameter ('sort=updated'). However, it adds no meaning for count, offset, book_id, or name_contains, and the sort explanation duplicates the schema text.

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?

States a specific verb ('List') and enumerates the exact resources (shelves, books, chapters, pages), so it is immediately distinguishable from the create_*/update_*/delete siblings. It also names the related read tool ('get') it is not.

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?

Explicitly states two use cases ('see what exists', 'find recently updated pages') and routes the agent to an alternative ('To see what's inside a book, use get on the book instead'). Both when-to-use and when-to-use-something-else are covered.

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