bookshelf_list_blocklist

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

The readOnlyHint annotation already indicates a safe read operation, and the description adds no additional behavioral context beyond repeating query parameter names. It does not explain pagination defaults, sorting behavior, or what constitutes a blocklist entry.

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 very short, but the second sentence is redundant with the schema's parameter list and does not add value. While concise, it sacrifices informative content, making the conciseness less effective.

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 simplicity, the description is minimal but lacks essential context such as what blocklist contains, any filtering semantics, or guidance on when to use it relative to similar list tools. The presence of an output schema helps, but the description still fails to provide sufficient situational context.

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 description merely lists parameter names using camelCase, while the schema uses snake_case, creating potential confusion. With 0% schema description coverage, the description was expected to explain parameter meanings, but it does not; it only restates names already present in the schema.

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 'List' and the resource 'blocklist', making its purpose unambiguous. It also distinguishes from sibling tools like 'bookshelf_delete_blocklist' and 'bookshelf_bulk_delete_blocklist'.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention any conditions or exclusions, leaving the agent to infer usage only from the tool name.

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