list_showcases

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

Annotations already communicate read-only, idempotent, and non-destructive behavior. The description adds useful conceptual context by translating the domain term 'showcases' to 'albums' and describing them as curated playlists with their own pages, which helps agents understand what they are operating on.

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, well-structured sentence that front-loads the action and resource, then adds valuable clarifying context. Every part earns its place with no redundancy or 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, read-only list operation with only optional parameters, the description is largely complete. It could optionally mention pagination or the return shape, but the schema already documents pagination fields, and the annotations cover safety behavior, so no critical context 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 description coverage is 0%, and the tool description does not mention any of the four parameters. The schema provides types, defaults, and enums, but the description adds no meaning or guidance about page, sort, per_page, or direction, so it fails to compensate for the missing parameter documentation.

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 lists showcases, immediately clarifies that the API calls them albums, and adds the defining trait that each is a curated playlist with its own page. This strongly distinguishes it from sibling tools like list_folders and get_showcase.

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 phrase 'List your showcases' establishes a clear use case: retrieve a collection of the user's own showcases. It does not explicitly name alternatives or exclusion conditions, but the context is clear enough for an agent to infer it is the right tool for listing rather than fetching a single showcase.

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