tiktok get shop catalog diagnostics

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

The description adds valuable behavior beyond the annotations: it discloses a fallback chain (catalog reporting → Shop auction metrics) and notes that endpoint warnings are returned when catalog permissions are unavailable. This supplements the readOnlyHint, openWorldHint, and idempotentHint without contradicting them.

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?

One compact sentence that front-loads the read-only domain and packs in the fallback behavior and warning behavior. Every part earns its place; there is no filler or repetition of annotation data.

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?

Given a fully described schema, an output schema, and annotations covering the safety profile, the description covers the essential behavioral complexity—fallback logic and permission warnings. The only notable gap is the lack of guidance for choosing this tool over the many reporting siblings, but that is a usage-guideline concern rather than a completeness gap for invoking it correctly.

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 the parameters are fully documented in the input schema. The description itself contributes no additional parameter-level semantics beyond what the schema already provides, which is acceptable at the baseline for high coverage.

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 identifies a specific domain—TikTok Shop/catalog/e-commerce diagnostics—and explains the core behavior of trying catalog reporting first, then Shop auction metrics. It is clear about the read-only nature, though 'diagnostics' is a noun rather than an explicit verb like 'retrieve' or 'get'. It does not explicitly contrast with sibling tools, but the scope is distinctive enough.

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 or when-not-to-use guidance is provided, and no alternatives are named relative to siblings like tiktok_get_insights or tiktok_get_report_raw. The phrase 'TikTok Shop/catalog/e-commerce diagnostics' implies a niche use case, but the description leaves the choice entirely to inference.

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