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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavior: results are aggregate totals across members, and the call returns empty with an explanatory reason when too few members have taste on file. The one gap is that it doesn't say whether results are ranked or how many are returned.

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?

Three short sentences, front-loaded with what is returned and followed by the use case and the empty-result edge case. Slightly compressed phrasing ("as totals") costs a little clarity but nothing is padded.

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, the description carries the return-value burden and does so reasonably: per-book fit counts, read counts, and an empty-with-reason condition. A note on ordering or result limits would make it complete for a recommendation tool.

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 100%, and the schema already explains that the club parameter accepts a siftivo.com/c/ link, a code, or a clubId. The description adds nothing about the parameter beyond implying a club is involved, so this is the baseline for a fully documented single-parameter schema.

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 uses a concrete verb-plus-resource framing: books matched to a club's members as a group, returned with per-book fit counts and read counts. That distinguishes it from personal-recommendation siblings like what_to_read_next and recommend_from_titles, though it never names those siblings explicitly.

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?

It anchors usage in a natural question ("what should my club read next?") and describes a concrete downstream step: pass the returned workIds to manage_club's open_poll. It lacks an explicit "don't use this when..." clause or a named alternative, so it stops short of full routing guidance.

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