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

Goes well beyond the annotations by disclosing the non-obvious write behavior: the first call each day sends passages to an AI provider, generates and stores the result in the reader's account, and counts against their AI usage quota, while later calls return the same data. This explains exactly why readOnlyHint=false while idempotentHint=true, and pre-empts surprises about quota consumption.

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?

Front-loaded with the return value, followed by the side-effect/idempotency fact, then a final usage sentence. Every clause carries information absent from the schema or annotations; the AI-provider detail, though wordy, is precisely the hidden cost an agent needs.

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?

An output schema exists, so the description need not enumerate return fields, yet it still characterizes the shape (theme plus question). Combined with the disclosed first-call generation and quota counting, an agent has everything needed to decide whether to call and what to expect.

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 tool takes no parameters, so there is nothing to disambiguate beyond confirming the implicit 'today' scoping, which the description does make clear. The zero-parameter baseline of 4 applies; no additional per-argument meaning is possible.

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?

States a specific verb and resource ('returns today's connections in the reader's reading') and then concretely describes the payload: passages from different books, saved quotes, a named theme, and a reflection question. This is distinguishable from siblings like find_related_passages or compare_books, which operate on explicit inputs rather than the reader's current multi-book state.

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?

Explicitly names the trigger: 'Use when the reader asks what connects their recent reading, or for today's reading connections or reflection prompt.' That is a clear usage context, but it stops short of naming alternatives or exclusions (e.g., when to prefer find_related_passages for a targeted passage lookup).

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