get_product

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

Describes the return content comprehensively (description, variants, images, reviews) and implies a read-only operation. No annotations are provided, so the description carries the full burden; it does not mention rate limits or auth, but for a simple fetch, this is sufficient.

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?

Single sentence, front-loaded with key verb and resource, no extraneous words. Every part earns its place.

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?

With one parameter and no output schema, the description covers what is returned, when to use it, and how the input works. Could mention pagination or review count, but overall complete for a simple tool.

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 100% with a clear description of 'handle' parameter. The description adds an example (URL slug format) but does not significantly enhance what the schema already provides. Baseline of 3 is appropriate.

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?

Clearly states 'Get full details... for a single Livostyle product by handle', listing specific content (description, variants, images, reviews) and distinguishes from siblings by noting 'Use after search'.

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?

Explicitly says 'Use after search to expand on a specific item', providing clear context for when to invoke this tool relative to sibling tools like search_products.

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