Get price

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds 'current price' implying real-time data, but does not disclose pagination, error handling, or rate limits. Minimal added value beyond the annotation.

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 a single sentence, concise but not optimally structured. It mentions the key action but lacks specificity about variants. Could be improved by front-loading the verb and adding brief context without being verbose.

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 the lack of output schema, the description should explain what the tool returns (e.g., price value, currency, variant details). It only states it gets the price, leaving the agent unsure of return structure. This is a significant gap for a simple tool.

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 coverage is only 50% (platform described, product_id not). The description does not explain the product_id parameter's format or constraints, nor does it clarify the platform parameter's role (though schema covers it). The description should compensate for the missing product_id description but does not.

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 the current price of a product and all its variants. This distinguishes it from sibling tools like update_price (modifies price) and get_products (returns broader product info). However, it could be more explicit about the scope (e.g., does it return any other product details?).

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 tool over alternatives such as get_products (which also returns price) or get_low_stock_items. No mention of prerequisites or context for choosing this specific tool.

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