apple_books_series

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

With no annotations, the description must carry behavioral disclosure. It states the data source is Apple Books' public catalog page, implying read-only public access, and specifies that it returns metadata and the full ordered list. However, it does not explicitly state that the operation is read-only, has no side effects, or requires no authentication, nor does it mention potential pagination or rate limits. The 'full ordered list' detail adds useful behavior, but gaps remain.

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 only two sentences, front-loaded with the action and resource, and includes essential return information. Every word earns its place; there is no redundancy or filler.

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?

For a straightforward retrieval tool with a fully documented schema, the description adequately covers purpose, return type, and data source. It does not explain how optional parameters like lang and country affect results, but the schema already does so. The lack of an output schema is mitigated by the clear statement that series metadata and the full ordered book list are returned.

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 input schema provides 100% parameter coverage: id is described as an Apple Books numeric series ID, lang as a result language tag, and country as a two-letter storefront country code. The description adds no additional meaning beyond restating the purpose, so the baseline of 3 for full schema coverage is appropriate.

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 tool's action ('Retrieve') and resource ('an Apple Books series and its full book list'), making it distinct from siblings like apple_books_audiobook_series by specifying 'book list' rather than audiobooks. It also notes the return of series metadata and the ordered list, which removes ambiguity.

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 implies when to use this tool (when series data and book lists are needed) and provides context via 'from Apple Books' public catalog page', but it offers no explicit guidance on alternatives or exclusions. It does not mention sibling tools like apple_books_book or apple_books_audiobook_series, leaving the agent to infer usage from purpose alone.

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