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

Annotations already declare a safe, non-destructive, closed-world read, so the bar is lower. The description usefully adds what the payload contains (rankings, weeks on chart, new entries) and that it is this week's edition, but says nothing about size, pagination, or how editions are keyed beyond the schema.

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?

Two sentences, no filler, with the scope and return contents front-loaded before the usage examples. Every clause earns its place.

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 tool with rich annotations there is little left to explain, and the description covers what comes back and when to call it. Without an output schema it could have said slightly more about the shape of the ranking, but nothing essential is missing.

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 coverage is 100% on the single week parameter, including the YYYY-MM-DD pattern and the omit-for-current guidance. The description adds no syntax or format meaning beyond that, so the baseline of 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 a specific resource (the Siftivo Reading Index) and spells out its content: fiction and nonfiction books ranked by cultural circulation, with weeks on chart and new entries. That is enough to separate it from search_books or the recommend_* siblings without opening any schema.

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 quoted intents ("what's popular right now", "what is everyone reading", "the big books this week") give a clear sense of when to reach for this tool. It never names an alternative or an exclusion, though, so the agent must infer that recommendation tools are for personalized rather than popularity queries.

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