get_must_hear_albums

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation through 'List' and discloses pagination behavior via 'one-based page number for more results' plus the omit-filter sentinel values. However, it does not mention result ordering, page size, or whether the list is curated/ranked, which would add useful behavioral context.

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 first sentence states the core purpose and optional filters, followed by a compact and readable args block. Every line earns its place, and there is no redundant or vague filler.

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 simple list tool with three optional parameters and an output schema, the description is largely complete: all parameters are explained, default behaviors are clear, and pagination is mentioned. The only notable omission is guidance about how this relates to sibling album-list tools, but that is a usage-guideline concern rather than a blocker for correct invocation.

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 0%, but the description explicitly defines every parameter: year is a release-year filter with 0 meaning 'omit', decade is a string like '1990s' with empty string meaning 'omit', and page is a one-based pagination parameter. This fully compensates for the bare schema and leaves no parameter meaning ambiguous.

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 a specific verb ('List') and resource ('AOTY's must-hear albums') and adds optional filtering by year or decade, which gives concrete scope. It does not explicitly contrast with sibling list tools like get_popular_albums or get_anticipated_albums, but the 'must-hear' category is distinctive enough to avoid real confusion.

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?

There is no guidance about when to use this tool versus alternatives such as get_popular_albums, get_anticipated_albums, search_albums, or get_critic_lists. The only usage-related information is about the optional filters, which is parameter guidance rather than tool-selection guidance.

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