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

Annotations already fully declare readOnlyHint, idempotentHint and destructiveHint, so the safety profile is covered. The one addition, 'runs no new diagnosis,' is genuinely useful because it warns the agent results may be pre-existing/stale. Still, there is no disclosure of pagination behavior, result caps, or what an undiagnosed listing looks like.

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 sentences with zero filler, front-loading the core action and return content before the read-only constraint. Every clause carries weight.

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?

With no output schema, the description usefully sketches the return shape (per-listing tier plus diagnosis codes). The remaining shortfall is operational detail: six parameters with no explanation of paging or the undiagnosed filter, which matters for correct 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 coverage is 50%, so page, per_page and filter_undiagnosed are undocumented in structured fields. The description partially compensates by naming the tier vocabulary (POOR, FAIR, GOOD), which supplies the enum values missing from filter_tier, but it says nothing about paging or what filter_undiagnosed selects, leaving real gaps.

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 ('Lists one TikTok Shop integration's listings') plus what comes back ('quality tier (POOR, FAIR, GOOD) and the diagnosis codes'). No sibling deals with TikTok listing quality, so differentiation is implicit rather than stated, which keeps it from 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?

'Read-only; runs no new diagnosis' implies this is for reading existing diagnosis state rather than triggering a refresh, which is a useful when-to-use signal. However, it names no alternative tool for actually running a diagnosis and gives no conditions or exclusions beyond that one clause.

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