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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a prerequisite (connected store Starter+) and a detailed breakdown of output categories: account data (price, inventory, FBA/FBM, status), observed/estimated market data, and price_vs_market classification. This goes beyond the annotations.

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?

The description opens with the core concept, then enumerates the output fields, then states the prerequisite and use-case triggers. Every sentence carries distinct value and it is compact for the information conveyed.

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 read-only list tool with no required parameters, the description adequately covers purpose, output fields, prerequisites, and example queries. There is no output schema, but the description enumerates the main data categories. Minor gaps are pagination/empty-state behavior and interpretation of 'sourcing score', but these are not critical for invocation.

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% and the three optional parameters are fully documented with defaults, enums, and marketplace ID meanings. The description adds no parameter-specific semantics beyond what the schema already provides, so the baseline of 3 applies.

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?

The description states a specific resource — the seller's own connected Amazon catalog — and what it does: shows exact account data alongside market intelligence and a price_vs_market read. The 'OWN' and 'your price, your inventory' wording clearly distinguish it from sibling tools like my_competitors or search_products.

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?

Explicit trigger phrases are given: 'Use when the seller asks about their own products, how am I priced vs the market, which of my products are under pressure, or show my catalog.' It also notes the Starter+ connected-store requirement. It doesn't name an alternative or state when not to use it, but the use cases are unambiguous.

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