get_duplicate_books

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

Beyond the readOnlyHint annotation, the description adds the significant behavioral constraint that ADMIN is required. It also implies hash-based grouping logic, which is useful context. However, it doesn't detail, for example, whether duplicates are detected across libraries or only within one, but the annotation and admin note cover the most critical behavioral aspects.

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 concise: two short sentences that immediately state the core functionality and a key prerequisite. There is no redundant information, and it is well-structured with the action verb front-loaded.

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 presence of an output schema (so return values need not be explained) and a readOnlyHint annotation, the description covers the essential context: what it lists, how it identifies duplicates, and the admin requirement. This is sufficient for a list operation with standard pagination parameters.

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?

With 0% schema description coverage, the description needed to compensate by explaining the parameters (page, size, sort, unpaged), but it does not. The parameter names are generic and self-explanatory to an experienced API user, but the description adds no additional meaning, leaving a clear gap in parameter documentation.

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 a specific action (List), a specific resource (duplicate books), and the mechanism (by file hash). This distinguishes it from sibling tools like get_book and search_books, making the tool's purpose unambiguous.

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 relative to other book listing tools, nor any exclusions or alternative suggestions. The only usage note is 'Requires ADMIN,' which is an access requirement rather than a use-case guideline.

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