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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the account-scoped notion of 'your own', which is modest extra context but says nothing about pagination, return format, or 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?

Five words is maximally concise and front-loaded, but here brevity crosses into under-specification rather than economy — the sentence earns its place but does not do enough work.

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 no output schema, an undescribed required array parameter, and no guidance on scope or alternatives, the definition leaves an agent missing key information for calling this tool correctly.

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 only 50%: skus is an undescribed array, and account_id's explanation is in Italian and lives entirely in the schema. 'Per SKU' hints at the skus input but adds no format, cardinality, or batching detail, so the description does not compensate for the coverage gap.

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 phrase 'Your own pricing per SKU' identifies the resource (the caller's own prices) and the granularity (per SKU), which implicitly separates it from get_competitive_pricing and get_buybox_prices. However it is a noun phrase with no explicit verb and no statement of what is returned, leaving the purpose only implied.

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?

There is no when-to-use guidance, no mention of the sibling tools that also return prices (get_competitive_pricing, get_buybox_prices, get_fee_estimate), and no prerequisites. An agent must infer everything 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.