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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered without description help. The description adds the useful detail of which qualification categories are returned, but says nothing about auth scoping, rate limits, or what happens when an advertiser is unqualified.

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 single sentence stating the return value, followed by a short pointer for the dependent parameter. No filler or repetition; the parenthetical enumeration earns its space by clarifying the notion of 'qualification.'

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?

An output schema exists, so return structure need not be described. However, for a read tool requiring two identifiers, the description leaves advertiser_id identity and any account-context requirements unexplained, leaving a meaningful gap.

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 0% for two required params. The description compensates for one of them by explaining bc_id's source (list_tiktok_business_centers), which is a genuine chaining hint, but advertiser_id is left completely undefined in both schema and description.

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: 'Returns an advertiser's qualification / verification status under a Business Center,' and enumerates the sub-signals (business verification, industry qualification, account standing). This clearly separates it from sibling listers like list_tiktok_bc_advertisers, though it never names an explicit alternative.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative tool. The only usage cue is the prerequisite chain hint ('bc_id from list_tiktok_business_centers'), which implies a two-step flow but does not state conditions for calling this tool.

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