Books by an author or translator

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

The description provides some behavioral context beyond annotations: it explains the 'no_current_offer: true' field and its typical meaning, which is helpful. The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description doesn't need to repeat that. It adds value by explaining a specific field in the output, even though it's not a full behavioral contract. It doesn't contradict annotations.

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 concise, with two sentences. The first sentence states the core purpose, and the second provides a practical tip. It is front-loaded with the main function. However, it could be slightly more structured, but it's still efficient and to the point.

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 complexity (4 parameters, one required, and a rich output with pricing), the description is fairly complete. It clarifies the author/translator nuance and hints at output fields. An output schema is not provided, so the description helps interpret responses. It lacks explicit details on pagination or sorting, but those are in the schema. Overall, it's adequate for an agent to select and use the tool correctly.

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 75%, meaning most parameters are described in the schema. The description does not add much about the parameters beyond the schema; it doesn't explain 'page' or 'limit' semantics further, but the schema already does. The description adds value by mentioning that entries are editions with price and discount, and the 'no_current_offer' field, which helps interpret results. For the 'person_id' parameter, the schema says it comes from find_author_publisher_or_tag or book_editions, which is clear. So the description adds slight value by explaining output semantics.

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 that this tool returns every edition an author wrote or a translator translated, distinguishing it from other tools like publisher_books and browse_tag. It also mentions the nuance that iranketab treats authors and translators as one profile, which is specific and informative. The verb 'find' is implied but the resource is very clear.

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 explains that the tool is for both authors and translators, and hints at using it when you need editions by a person. It mentions confirming out-of-stock status with book_editions, which gives context for when to use that alternative. However, it doesn't explicitly say when not to use this tool compared to similar_books or search_books, but the sibling list is small and the description gives enough context to make a decision.

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