run_target_products_search

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

With no annotations the description carries the full burden, and it does add real behavioral context by disclosing 'live' data and a cost model ('1 point per returned record'). However, it omits return format, pagination behavior, and any auth or rate-limit context, leaving meaningful gaps.

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?

Two compact clauses, front-loaded with the verb and resource. It is efficient and free of filler, though the parenthetical sort list is partly redundant with the schema enum.

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?

For a 4-parameter search tool with no output schema and no annotations, the description covers the core purpose and cost but says nothing about return shape or pagination semantics. Adequate but with clear gaps given the absence of structured safety/output metadata.

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 100%, so the schema already documents keyword, sort (with enum), max_items, and start_page. The description restates the sort values, which is redundant, and adds no syntax or interaction detail (e.g., how start_page and max_items combine). Baseline 3 is appropriate.

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 (Search) and resource (live Target products) plus the keyword mechanism, so an agent can identify it as the search variant of the Target toolset. It does not explicitly differentiate itself from siblings like run_target_products or run_target_categories_products, so it stops short of a 5.

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, prerequisites, or named alternatives are given. The agent is left to infer that this is the keyword-search entry point versus the detail tools in the family (run_target_products, run_target_products_reviews).

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