Get Galaxus product details

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

With no annotations provided, the description must convey behavioral traits. It clearly indicates a read operation via 'Fetch' and lists output fields, but does not disclose error handling, rate limits, authentication requirements, or behavior for invalid/missing products. It adds some context but leaves gaps typical for a simple fetch tool.

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?

One concise, front-loaded sentence that states the action, input, and output details. No filler or redundancy; every part contributes to understanding the tool's function.

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 tool with a single parameter and no output schema, the description covers the core purpose, accepted inputs, and returned data fields. It lacks explicit error/edge-case behavior, but overall it is sufficiently complete for an agent to invoke successfully in most scenarios.

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 schema already describes the single parameter idOrUrl with 'Galaxus product id, slug, or full product URL' (100% coverage). The description echoes this and adds the nuance 'numeric id', but does not meaningfully enrich the parameter understanding beyond the schema.

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 uses a specific verb+resource ('Fetch full details for a single product') and enumerates the exact data fields returned (description, GTIN, specifications, images, rating, availability, price history). It clearly distinguishes from sibling tools like search_products (which lists products) and check_price_availability (which focuses on price/availability only).

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 when needing comprehensive details for one specific product, and mentions accepted input formats (id, slug, URL). However, it does not explicitly name alternative tools or state when not to use it, though the context makes the intended use clear.

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