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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: data is read LIVE from Amazon, issues are classified by severity (not sellable / hidden from search / attribute hidden), and fixes are mapped to a door (draft text, attribute, image, Seller Central case, category approval). It stops short of disclosing latency, rate limits, or failure modes when a listing cannot be resolved.

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?

Front-loaded with the core purpose and the when-to-use rule, with the long parenthetical enumerating fix doors earning its place by previewing the output. It is dense but well-ordered; the final 'Its `narrative` is the answer' sentence could be tightened.

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?

There is no output schema, so the description carries the return-value burden and does so thoroughly: the shape of each problem (severity, fix door, schema requirements, current value, patch skeleton) and the pointer to the `narrative` field. Combined with the usage ordering, an agent has everything needed to call it and interpret the result.

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 sku, account, and marketplace_id are already documented in the schema. The description adds no meaning about how account/marketplace scoping affects the lookup, so it sits at the baseline for a fully described schema.

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+resource: it returns one listing's problems and the exact fix for each, read live from Amazon. It explicitly distinguishes itself from the sibling get_listing_issues by positioning itself as the follow-up that supplies fixes.

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?

Gives an explicit ordering rule: 'Use it after get_listing_issues, before drafting any listing fix.' Both the trigger and the downstream alternative (drafting a fix directly) are named, so the agent knows when to call it and when not to.

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