get_current_rank

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

The description uses 'Read', implying a non-destructive, read-only operation. However, no additional behavioral traits (e.g., rate limits, caching, data freshness) are disclosed. With no annotations provided, the description carries the full burden but only minimally addresses 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?

A single, front-loaded sentence of 12 words that efficiently conveys the core functionality. Every word serves a purpose; no extraneous information.

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 lists the return information (organic position, sponsored position, total result count) but does not specify the structure (e.g., separate fields, numeric values). Given no output schema, this is adequate but not fully complete for an AI agent to understand the exact output format.

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 two parameters 'asin' and 'keyword' are standard and self-explanatory, but the description does not elaborate on their format (e.g., Amazon standard ASIN, exact match keyword) or constraints. Schema coverage is 0%, so the description adds some context by implying they are the inputs for the rank lookup.

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?

Clearly states the verb 'Read', the resource 'live keyword rank for an ASIN', and specifies the returned data: organic position, sponsored position, and total result count. This distinguishes it from sibling tools like get_keyword_performance which may return aggregated metrics.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., get_keyword_performance or get_search_terms). No when-not scenarios or prerequisites are mentioned.

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