reading_card_collection

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

Annotations already declare readOnlyHint=true, and the description does not contradict this. It adds some useful behavioral context by stating the collection is paginated and scoped to 'collected' cards, but it does not disclose details about ordering, response shape, or how pagination behaves.

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?

A single sentence that is front-loaded with the core action and resource, and it wastes no words. It earns its place by communicating the essential distinction without opening every image.

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?

With no output schema and three undocumented parameters, the description is too sparse to fully support correct invocation. It does not explain what limit/offset/bookId control, how 'collected' relates to the bookId filter, or what the paginated response will look like. The read-only annotation helps, but the description still leaves significant gaps.

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 description coverage is 0%, so the description must compensate for the three undocumented parameters. It only implies limit and offset through the word 'paginated' but provides no meaning for bookId or the parameter semantics. This leaves an agent with little guidance for constructing correct calls.

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 identifies the action (browse), the resource (collected reading cards), and the mode (paginated collection). It also contrasts with opening every image, which helps distinguish it from more granular viewing tools. However, it does not explicitly differentiate itself from the similarly named sibling reading_list_cards.

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 phrase 'without opening every image' implies this is for high-level browsing rather than inspecting individual cards, giving some situational context. It does not explicitly state when to prefer this tool over alternatives such as reading_list_cards or reading_open_card, nor does it mention exclusions or prerequisites.

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