Resolve Shopee short product links by validating each redirect before querying product IDs, enabling accurate product URL parsing for affiliate workflows.
Resolve link curto Shopee, validando cada redirecionamento antes de consultar IDs.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| mode | Yes | ||
| synthetic | Yes | ||
| account_reference | Yes |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds process context by saying each redirect is validated before IDs are queried, but it omits auth needs, rate limits, and error behavior.
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?
One front-loaded sentence with no wasted text. It is appropriately sized for a simple resolution tool, though adding a brief usage clause would improve structure without excessive length.
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 rich annotations and an output schema, the description need not cover returns or safety. However, for a 1-param tool with 0% schema description coverage, it should say more about the URL format and when to choose this tool over siblings.
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 0%, so the description must carry the burden. It identifies the input as a Shopee short link, which gives the url parameter useful meaning beyond a plain string, but it provides no format example or constraint details.
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 (resolve) and resource (Shopee short link), plus an internal validation step. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling parse_product_url.
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 when-to-use or when-not-to-use guidance is provided. The short-link phrasing implies a context, but it does not name alternatives like parse_product_url or explain which URL types select this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.