get_store_customer

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds context about authentication (API key) and rate limiting (max 10 concurrent requests), plus 'safe to retry'. This adds value beyond annotations, though it doesn't address the 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?

Description is well-structured with a purpose sentence, usage sentence, auth/concurrency info, and a bullet-style Args section. Every sentence adds value, no redundancy.

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?

Given the tool is a simple single-record retrieval with an output schema (indicated), the description covers how to use it, how to get IDs, authentication, concurrency, and return format. It is complete for its 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?

Despite 0% schema coverage, the description fully explains every parameter: store_id as 'E-commerce store ID', customer_id with source ('Obtain from list_store_customers'), and account with environment variable configuration and default behavior. This adds significant meaning.

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 verb 'Retrieve' and the resource 'single store customer' with specific fields (email, opt-in status, order totals). It distinguishes from sibling list_store_customers by focusing on single record retrieval.

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 ('inspect customer purchase history and subscription state') and when to use alternative ('use list_store_customers to browse and discover customer_ids'). Also provides authentication and concurrency limits.

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