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

Annotations already carry the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not required to restate them. But it adds nothing beyond them: no mention of pagination defaults, ordering, or what happens when a location has no assigned books, leaving it a pure restatement of the name.

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 front-loaded sentence with no wasted words. It is tight, though the brevity stems partly from under-specification rather than disciplined editing.

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 return values need not be explained, but the tool still has three parameters at 0% description coverage. For a paginated location-scoped list tool in a crowded sibling namespace, the description leaves out pagination behavior and disambiguation guidance that an agent needs to call it correctly.

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 schema documents none of the three parameters, and the description only hints that locationId is the site identifier. The limit and offset pagination parameters (with defaults and caps) are completely undocumented in both places, and the description does nothing to compensate.

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?

'Read a site's assigned books' names a specific verb and resource with a scope qualifier (assigned to a site), which distinguishes it from the general list_books in substance. However, it never names the sibling or states the distinguishing condition explicitly, so an agent must infer the difference.

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?

There is no statement of when to use this tool versus list_books, get_book, or the many other location-scoped list tools. The single sentence implies usage ('when you want books for a site') but offers no exclusions or prerequisites such as needing a valid locationId.

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