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

Annotations already mark this as readOnly and openWorld, but the description adds useful behavioral context beyond them: it will not invent Associates tags and omits tag= until real server-configured IDs exist. It also discloses that marketplace choice changes the output from a /dp link to a Mother's Day search deep-link.

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 short and front-loaded with the core conversion behavior and required parameters. The trailing 'OpenAPI: resolveProduct' reference is slightly extraneous but not disruptive.

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 read-only resolver with no output schema and nine parameters, the description covers the main input modes, required parameters, output link types, and tag behavior. It does not explain the optional refinement parameters (styleTag, budgetBand, occasion, preferSearch), which is a remaining gap but not a fatal one.

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?

The description maps the three main input modes to url, asin, and keywords, and emphasizes that marketplace and locale are always required. But with schema coverage at 56%, it leaves occasion, styleTag, budgetBand, and preferSearch without added meaning beyond their enum values.

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 states a specific verb and conversion target: resolve an ASIN, pasted Amazon /dp/ URL, or keywords into a buyUrl, including the two possible output forms (/dp product link or Mother's Day search link). This is clearly distinct from sibling tools like search_gifts or suggest_gifts, though no sibling is named explicitly.

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?

It gives the concrete input modes (ASIN, pasted URL, keywords) and a required-parameter instruction: 'ALWAYS pass marketplace + locale.' However, it does not state when to prefer this tool over search_gifts, suggest_gifts, or get_catalog, so the selection guidance is only implied.

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