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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the REST endpoint (GET /api/v1/stock/{account}/book), with no disclosure of result volume, defaults, or pagination limits beyond what the schema already says.

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 short sentences: what it is, how to narrow, how to page. No filler, and the defining content (movement ledger with fields) comes first.

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 7 optional params, no output schema, and no required arguments, the description does enough: it sketches the returned record fields and points at next_query for paging. A note on result ordering or default page size would close the remaining 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%, so every parameter is already documented in detail (ISO formats, 1-100 limit, next_query semantics). The description's mention of product/location/period/text filters and next_query only mirrors the schema without adding syntax or edge-case meaning.

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?

Names the resource precisely ("Stock book: every stock movement") and enumerates the movement kinds (sale, delivery, correction, transfer) plus the fields carried (product, location, quantity, date). This distinguishes it clearly from tillhub_list_stock, which is about current levels rather than the movement ledger.

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 filtering and paging hints but never states when to prefer this over tillhub_list_stock or tillhub_list_stock_locations, nor any exclusions. Usage is implied by the movement-ledger framing rather than spelled out.

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