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

No annotations, so the description carries the full burden. It adds one genuinely useful behavioral fact — '1 point per returned record' (a cost/quota disclosure) and that results are 'live'. It says nothing about pagination behavior, result format, or any rate/auth constraints, leaving meaningful gaps for a search endpoint.

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 tight sentence front-loads the core action and the sorting dimension, with the cost note appended without padding. Nothing is wasted.

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?

No output schema exists and no annotations are provided, so the description should do more. It covers the action, sort, and cost, but omits pagination behavior (start_page/max_items) and any indication of what a record contains — relevant given the many sibling search tools an agent must choose between.

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 the schema already documents keyword, sort (with enum), max_items, and start_page. The description echoes the sort options, which adds nothing beyond the schema. Baseline 3 applies since the schema does the heavy lifting.

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 (search Target products) with a scope qualifier ('live') and names the primary dimension (keyword, sort). An agent can distinguish this from run_target_products (single product lookup) without opening the schema, though no sibling is explicitly named.

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 when-to-use guidance, no prerequisites, and no routing among the many sibling *_product_search tools (Walmart, Amazon, eBay, etc.). The agent must infer context entirely.

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