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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: a one-hour cache, and the caveat that a past rotation can still hold evergreen catalogue items whose `market_price` and `is_available_on_store` reflect today rather than the rotation date. That temporal caveat meaningfully guards against misinterpretation.

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 core statement is front-loaded in one short sentence, followed by the payload breakdown. The inline field enumeration is compact, though the long parenthetical about itemdefid_count and evergreen items makes the second sentence heavy for what it conveys.

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 does the heavy lifting by describing the return envelope, item buckets and shared item shape. Only the pagination/size characteristics are unaddressed, which for a single-rotation lookup is a minor omission.

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% and the parameter already carries an example, maxLength and a description pointing to /store/history. The description's field listing describes the response, not the `rotation_id` input, so it adds little semantic value beyond the schema — baseline 3.

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 states a specific resource ('one rotation's full item list') and enumerates the rotation envelope fields plus the three item buckets, so an agent knows exactly what comes back. It does not name a sibling to contrast with, though 'One rotation as the wiki's /store/rotation page shows it' implicitly separates it from get_item_store history/browse tools.

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?

Usage is implied rather than stated: the id format 'from /store/history' hints at the prerequisite call without naming get_item_store_history as an alternative. There are no explicit when-not-to-use rules or stated alternatives, so the agent must infer selection.

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