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

Annotations already supply readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuine value beyond that: 'Free — no key, no allowance' discloses auth and rate-allowance behavior, and the pools explanation ('canonical reconciliation of every count this server quotes, so two totals are never mistaken for a contradiction and never added together') is a real behavioral caveat about how returned numbers relate to each other. No contradiction with the annotations.

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 scope is front-loaded ('Everything published on shpbl.com in one read') and the enumerated contents each earn their place by telling the agent what data to expect. The closing 'Free — no key, no allowance' is a compact, high-value statement. The first sentence is a long run-on held together by colons and commas, which is the only structural downside.

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 burden of describing returns, and it does so well by enumerating the data shapes for editions, volumes, downloads, case studies, and pools. All three optional parameters are explained, and the read-only/idempotent annotations complete the picture. The one gap is the 'facts' section in the sections enum, which is never explained in either the description or the schema.

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 baseline is 3 — the schema already explains volume, sections (including the pools reconciliation note), and case_study fully. The description adds only color about what each section contains (prices and licences, seals and read links, byte sizes, verdicts), which is mildly helpful but does not materially compensate for or clarify anything the schema misses.

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 resource ('everything published on shpbl.com') and frames the tool as a single-read index of editions, volumes, downloads, case studies, and pools. It is clear the tool is a compound catalog/read operation, and the schema note that a volume's complete text is a `library_document` call helps separate it from that sibling. It stops short of a crisp imperative verb like 'list' or 'return the index of', which keeps it from a 5.

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 gives explicit usage paths: 'Scope it with `sections`, or pass `volume` (slug or 1-7) or `case_study` (slug) for one record in full.' It also gives a concrete when-to-use rule for pools ('read it before comparing two totals') and states no key or allowance is needed. It does not explicitly state when to prefer a sibling like library_search, so exclusions/alternatives are only implied rather than named.

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