get_store_product_variant

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

Description adds value beyond annotations by specifying 'Read-only, safe to retry', 'Max 10 concurrent requests', and 'Authenticated via API key'. Annotations only provide hints (readOnlyHint=true, destructiveHint=false), so description enriches behavioral context. However, 'safe to retry' contradicts idempotentHint=false annotation.

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?

Well-structured with front-loaded purpose, followed by usage, auth, args, and returns. Every sentence adds value, no redundancy. Appropriate length for a single-variant retrieval tool.

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 4 parameters and an output schema, the description covers all necessary context: what it does, how to get variant IDs, authentication, concurrency limits, parameter explanations, and return format. No gaps.

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?

With 0% schema description coverage, the description compensates by explaining each parameter: store_id is 'E-commerce store ID', product_id is 'Product ID that owns the variant', variant_id comes from list_store_product_variants, and account is optional with configuration details. This adds meaningful context beyond the bare 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 clearly states the tool retrieves a single product variant with its price, SKU, and inventory details, using precise verb 'Retrieve' and resource 'product variant'. It distinguishes itself from the sibling list_store_product_variants by specifying this is for a single variant.

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 tells when to use this tool ('inspect one variant's attributes') and when to use the alternative ('Use list_store_product_variants to browse and discover variant_ids'). Also provides authentication and concurrency context.

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