tiktok_get_shop_catalog_diagnostics

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states the operation is read-only, describes the endpoint fallback order (catalog reporting first, then Shop auction metrics), and discloses that warnings are returned when catalog permissions are unavailable. This is meaningful behavioral transparency beyond the basic 'get' operation.

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 is a single, information-dense sentence with no filler. The core purpose is front-loaded, and every clause adds value: read-only safety, endpoint attempt order, and warning behavior.

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 9-parameter tool with no annotations and no output schema, the description gives useful behavioral context but lacks response format expectations, param selection guidance, and clearer failure semantics. The fallback warning detail helps, but an agent would still need to infer much from the schema and runtime results.

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 78%, so most parameters are already documented in the schema. The tool description itself adds no parameter-level meaning beyond the schema. The 22% gap is minor, but the description does not compensate for it; baseline 3 is appropriate.

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 clearly identifies the tool as read-only TikTok Shop/catalog/e-commerce diagnostics with a specific resource and action. It does not explicitly differentiate from siblings like tiktok_get_targeting_catalog or tiktok_get_report_raw, but the 'diagnostics' framing and catalog/Shop scope make the purpose reasonably distinct.

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?

The description provides a general context (TikTok Shop/catalog diagnostics) but no explicit guidance on when to use this tool over alternatives, nor any exclusions or prerequisites. The fallback behavior is described, but not the conditions that should lead an agent to select this tool instead of a sibling.

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