get_customer_profile

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

No annotations are provided, but the description discloses that the tool calls five Shopline APIs internally and returns a dict with specific data sections. It mentions amounts are floats in TWD. While it doesn't discuss rate limits or performance, the behavior is well-described for a read-only operation.

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?

The description is concise and well-structured with sections for purpose, usage, API calls, and return structure. It front-loads the key information and every sentence adds value.

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 there is no output schema, the description adequately explains the return structure (dict with five sections). It also lists the internal APIs called. The tool is read-only, and the description provides complete context for an AI agent to use it correctly.

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?

There is only one parameter (customer_id) with a description in the schema that explains it's the internal ID from list_customers. The tool description does not add additional semantics beyond the schema. With 100% schema coverage, baseline is 3.

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 customer's complete profile including basic info and multiple data sections. It uses specific verbs ('取得') and lists the five sections. It distinguishes from the sibling get_rfm_analysis for batch analysis.

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 provides usage context: answering questions about a customer's profile for customer service or individual analysis. It also directs to get_rfm_analysis for batch analysis, giving a clear when-to-use and when-not-to.

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