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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety and external-call profile is covered. The description adds that the lookup is live against Amazon's catalog (freshness/latency implication) and that a target ASIN gets its position highlighted, but says nothing about rate limits, throttling, or what happens when no results are returned.

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?

Three short sentences, the live/real-time qualifier and the core action are front-loaded, and nothing is padded. The middle sentence about returning top results from Amazon's catalog partly duplicates what the output schema conveys, a minor redundancy.

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 an output schema present and rich annotations, the description need not explain return values or safety. It covers the live-query nature and the ASIN-highlighting behavior, which is sufficient for correct invocation, though it omits any note on result limits or noisy-data conditions the diagnostics flags imply.

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 100%, so all five parameters including max_pages, include_raw_rows and include_diagnostics are already documented in the schema. The description only restates target_asin's highlight behavior, adding no format, default, or interaction detail beyond the 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?

States a specific verb and resource — check the current search rank position for a keyword — and the 'real time' framing implicitly contrasts with the historical sibling get_keyword_ranks. It never names that sibling, so the differentiation is left to inference rather than made explicit.

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?

Usage is implied by 'in real time', suggesting this is the tool for a live rank snapshot rather than batch/historical reporting. There is no explicit when-to-use statement, no exclusion, and no pointer to get_keyword_ranks or get_sales_ranks when a live query is not what the agent wants.

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