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

No annotations are provided, so the description carries the full burden. It discloses the key caveat that tt_account_id values are not identity_id values, explains that complete describes pagination not sync coverage or permission, and describes the pagination contract including cursor invalidation. Doesn't describe auth or rate limits, but these are less critical for a cached list 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?

Compact and dense, with the most important information front-loaded. Every sentence carries meaning. Slight redundancy: 'REQUIRED: none' is somewhat unnecessary given the schema shows no required params, and the example is helpful but minimal.

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 list tool with no output schema and no annotations, it's reasonably complete. It tells the agent what the tool returns (cached accounts), how to paginate, how to filter, and when NOT to use it. Missing details like exact response format or auth are reasonable gaps given it's a read-only list operation.

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%, so the description must compensate. It does: explains limit default/maximum, cursor semantics (from previous response, rejection/old cursor requires restart), and search (case-insensitive native id/name lookup). However, it doesn't describe the response shape or what 'compact bounded page' means precisely.

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+resource (list cached TikTok accounts from Business Center assets) and adds a crucial scoping caveat: these are not identity_id values. It doesn't explicitly contrast with all siblings, but the content clearly distinguishes it from assets_list_identities. Loses a point for not naming more siblings 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?

Provides explicit when-to-use guidance: for ad creation, use assets_list_identities with exact advertiser_id, and preserve identity_type and identity_authorized_bc_id. It also explains pagination behavior (follow next_cursor serially until complete=true) and error handling (rejected/old cursor requires restarting from page one). This is strong, actionable usage guidance.

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