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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the cross-account aggregation nature of the result set, which is modest additional context but no auth, rate-limit or return-shape detail.

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 short sentences, zero waste, with the scope qualifier front-loaded and the parameter provenance second. Nothing superfluous.

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 values need not be described, and the one required parameter's origin is documented. Adequate for a simple read-only list tool, with only minor gaps (ID format, behavior when bc_id is unknown).

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 0% for the single bc_id parameter, so the description must carry the burden, and it does by pointing to list_tiktok_business_centers as the source of the value. That materially reduces misfires, though it doesn't state the expected format (numeric vs string ID).

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 every pixel') plus the scope ('across a TikTok Business Center'), which is a real distinction. It does not explicitly name sibling list_tiktok_pixels, so the agent must infer the difference from the 'cross-account' phrasing.

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 tells the agent where bc_id comes from ('list_tiktok_business_centers'), which is useful prerequisite guidance. It gives no explicit when-to-use versus the per-account list_tiktok_pixels sibling, so selection still requires inference.

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