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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds domain context about what an asset group represents, but says nothing about pagination, result volume, or edge cases. Adequate given the annotations carry the behavioral burden.

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 dense but front-loaded sentence: the action and resource come first, the clarifying parenthetical second, and the parameter hint last. Nothing is padded, though the nested parenthetical slightly slows parsing.

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 no explanation, and annotations cover the safety profile. For a one-parameter read-only lister, the description supplies the resource definition and parameter source, leaving nothing essential an agent needs in order to call 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 coverage is 0% and the schema itself only says bc_id is a string, so the description must add meaning — and it does by telling the agent the value's provenance ('from list_tiktok_business_centers'). With a single parameter this provenance is the most useful semantic addition possible.

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 clear verb (Lists) and resource (asset groups) and goes further by defining what an asset group is — 'groupings of advertisers / pixels / identities used for bulk permissioning' — scoped to the TikTok Business Center. This is specific enough to separate it from the many other list_* TikTok siblings, though it does not name one explicitly.

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 closing note 'bc_id from list_tiktok_business_centers' implies usage (call the parent lister first) but the description never says when to use this tool versus adjacent listers like list_tiktok_identities or list_tiktok_bc_advertisers. Usage is implied through the dependency, not stated.

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