Retrieve full profile details for a specific Loyverse customer by passing their UUID.
Get full details of a specific customer by their ID
| Name | Required | Description | Default |
|---|---|---|---|
| customer_id | Yes | The customer UUID to look up |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint=true annotation already establishes this is a safe lookup. The description adds essentially nothing beyond that: no indication of what 'full details' contains, no behavior for a missing or malformed customer_id, and no pagination/return notes.
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?
A single efficient sentence, front-loaded with the verb and resource, with no wasted words.
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 one-parameter read tool with no output schema, the description covers the essentials but omits what 'full details' actually returns and how not-found or invalid-ID cases behave. Adequate but with clear 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?
Schema description coverage is 100%, and the schema already documents customer_id as 'The customer UUID to look up' with minLength 1. The phrase 'by their ID' merely restates this, so baseline 3 applies.
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?
States a specific verb and resource ('Get ... a specific customer') plus the lookup key ('by their ID'). It is clearly distinct from the sibling list_customers, though it never explicitly names that alternative.
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?
No guidance on when to use this versus list_customers or the other get_* siblings, and no prerequisites or error conditions mentioned. Usage must be inferred from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.