intelligence-api

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

No annotations provided, so description carries full burden. It adds valuable behavioral context by disclosing specific analyses performed (FBA fee estimate, profit margin, opportunity tier). However, missing operational details like error handling for invalid ASINs, caching behavior, or rate limits.

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 sentences with zero waste. First sentence establishes scope and input method; second sentence lists specific analytical outputs. Every word earns its place—no filler or 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?

For a 2-parameter tool without output schema, the description adequately compensates by listing key return values (FBA fees, margins, opportunity tier). Would benefit from mentioning error cases (invalid ASIN) or default marketplace behavior, but sufficient for tool complexity.

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%, establishing baseline 3. Description mentions 'by ASIN' which reinforces the required parameter, but adds no additional semantic detail about marketplace selection or ASIN format beyond what the schema already provides.

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?

Description provides specific verb ('Deep analysis'), resource ('Amazon product'), and distinguishing scope ('single' vs siblings, 'by ASIN'). The 'single' and 'ASIN' qualifiers clearly differentiate from amazon_search, while 'Amazon' differentiates from shopify tools.

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 explicit when-to-use or when-not-to-use guidance. The term 'single' implies distinction from amazon_search (likely for bulk/multiple), but lacks explicit guidance like 'use this when you have a specific ASIN; use amazon_search to discover products'.

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