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

Beyond the readOnlyHint annotations, the description discloses that the response is permission-scoped: anonymous callers get a public preview, linked members additionally get the current read, next meeting, open poll and pinned host message. It also states hard exclusions (no chat messages, no other members' names), which is exactly the kind of behavioral detail annotations cannot express.

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 sentences, front-loaded with the resource and key, then usage examples, then access behavior and exclusions. No sentence is redundant and the ordering is sensible.

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 one-parameter read with 100% schema coverage and no output schema, the description does the remaining work: it explains what the payload contains at each access level and what is deliberately withheld. There is no gap an agent would need to guess at before calling it.

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%, so the accepted forms (link, code, or clubId) are already fully documented in the schema. The description only echoes "by its link" and adds no format or normalization detail beyond that, so baseline 3 applies.

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 names the resource (a book club) and its lookup key (its link), and the eligibility split between public preview and member view clarifies what kind of read this is. It doesn't explicitly contrast itself with get_my_clubs or manage_club, so an agent must infer that this is the single-club lookup rather than a listing or mutation.

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 gives concrete example questions the tool answers ("what are we reading?", "when do we meet?"), which is strong when-to-use guidance for an agent. It stops short of naming alternatives or stating when not to use it, so the routing is implied rather than fully specified.

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