get_bundle

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

With no annotations, the description carries full disclosure burden. It correctly indicates a read operation and outlines the return fields, but lacks details on error handling (e.g., if product_id is not a bundle) or other behavioral traits like idempotency. It is adequate but not exhaustive.

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?

Two sentences deliver all essential information: the tool's output and a critical usage hint. No unnecessary words, front-loaded with purpose.

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-by-ID tool with no output schema, the description fully explains the returned fields and provides crucial context about bundle discoverability. No gaps are evident given the tool's low complexity.

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 0%, and the description does not elaborate on the single parameter product_id beyond its implicit meaning from context. While the parameter name is self-explanatory, the description adds no additional meaning, failing to compensate for the missing schema 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 reads a bundle's make-up, listing specific fields (SKU, Name, Components) and distinguishes bundles from regular products via a note about their hidden nature. It uses a specific verb and resource, differentiating it from siblings like get_product and list_products.

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 explicitly advises that bundles are hidden from product search and provides the alternative method (list_products or by ID) to find them. This gives clear context for when to use this tool, though it does not explicitly list exclusion scenarios.

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