wowaudit_get_loot_history

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety. The description adds value by listing the types of data included (recipients, awards, etc.), which is beyond the annotations. However, it does not mention pagination behavior or limits, which are partially covered in the schema description for the limit parameter.

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 description is a single, clear sentence that efficiently conveys the tool's purpose and key output details. No unnecessary words or repetition. Slightly more detail could be added without harming conciseness, but it's well-structured.

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?

Given the simple nature of the tool (2 params, read-only, output schema exists), the description adequately covers what the tool does and what it returns. The schema and annotations fill in the remaining details. Could mention that seasonId is required, but that is already in the schema.

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?

Both parameters have detailed descriptions in the schema (100% coverage), including the seasonId reference to another tool and the limit behavior with pagination note. The tool description does not add any additional parameter-level information, so 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?

The description clearly states the tool retrieves loot awarded during a keystone season, listing specific included fields (recipients, award responses, old items, notes, wishlist values). This distinguishes it from sibling tools like wowaudit_get_character_history (individual character) and wowaudit_list_historical_data (broader history).

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 implies use when needing loot history for a season, but does not explicitly differentiate from alternatives like wowaudit_get_character_history or wowaudit_list_historical_data. No direct guidance on when to prefer this tool over others.

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