list_bundles

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

No annotations are provided, so the description must carry the behavioral burden. 'List' reasonably implies a read-only operation, and the description reveals that results include use cases and one-time-purchase links. However, it does not mention pagination, data freshness, or any side effects, leaving some behavioral detail undisclosed.

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 sentence that front-loads the main action ('List product bundles') and adds clarifying detail immediately. There is no filler, repetition, or unnecessary information.

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 parameterless listing tool with no annotations and no output schema, the description provides sufficient context: it identifies the resource (product bundles), clarifies their nature (themed household datasets), and states what is returned (use cases and one-time-purchase links). Given the low complexity, nothing critical 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?

The tool has zero parameters and the input schema is empty, so no parameter documentation is needed. Baseline 4 applies because there are no parameters for the description to elaborate on; the description's mention of bundle content does not contradict or omit any parameter information.

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 verb and resource: 'List product bundles (themed household datasets)'. It clarifies that bundles are themed household datasets, which distinguishes them from sibling tools like list_archetypes and list_reference_parameters. The mention of included use cases and purchase links further defines the scope.

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 usage: if you need product bundles with use cases and purchase links, use this tool. However, it does not explicitly state when to use it instead of alternatives such as list_archetypes or get_purchase_link, and it offers no exclusions or conditions.

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