get_product_details

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals return field types and the precedence rule, but does not mention authentication, error handling, or side effects. As a fetch operation it implies read-only, but this is not explicit.

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 two concise paragraphs with a clear front-loaded purpose and a focused argument list. Every sentence adds value; no fluff or repetition of schema details.

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?

The description covers purpose, params, and precedence, and the presence of an output schema covers return details. It does not specify behavior when neither parameter is provided, which is a minor gap for a tool with zero required parameters.

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 schema has 0% description coverage, so the description fully compensates. It explains that product_id is a numeric id from search_products and takes precedence, and that url is a full tokopedia.com URL used as a fallback. This adds meaningful usage guidance beyond the raw schema.

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's action ('Fetch full details for one Tokopedia product') and lists the specific data fields returned (price, description, variants, stock, media, shop info). This distinguishes it from sibling tools like get_product_reviews and search_products, which serve different purposes.

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 provides clear context for when to use the tool, indicating that product_id comes 'from search_products' and that it takes precedence over url. It implies usage after searching for products, though it does not explicitly mention alternatives like get_product_reviews or specify when NOT to use the tool.

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