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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond that: it requires a linked Siftivo account and discloses that private notes and ratings are included in the payload. It says nothing about library size or result caps.

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 tight sentences, front-loaded with the resource and payload, then usage intents, then the prerequisite. Every sentence carries information; nothing is padding.

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 usefully enumerates the returned fields and states the auth prerequisite, which is enough for an agent to call it correctly. It omits any indication of volume, pagination, or ordering for a potentially large library, which is the only real gap.

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 single status enum is already fully documented with its own 'Omit for the whole library' note. The description's "Filter to one shelf with status" slightly reinforces the shelf-to-status mapping but adds no format or behavioral detail beyond the schema. Baseline 3 is appropriate.

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 — the signed-in reader's Siftivo shelves — and enumerates the four shelf categories plus the payload (ratings, progress, private notes). It is clearly distinguishable from single-item siblings like get_my_book and from get_my_taste.

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?

Gives concrete intent examples ("what am I reading", "what is on my to-read list", "what have I finished") and the prerequisite of a linked Siftivo account, plus when to use the status filter. It never names a sibling alternative or an exclusion case, so it stops short of a 5.

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