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

With no annotations, the description carries the full burden and delivers well beyond the obvious: it explicitly frames the operation as read-only, reveals that connection.email reflects the token-resolved auth account, and warns that a mismatch means the token is bound to the wrong account rather than a user switch. This prevents a likely misinterpretation.

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 purpose is front-loaded in the first sentence, and the TOKEN-IDENTITY CHECK, REQUIRED, and EXAMPLE sections are compact and each add actionable value. There is no filler or repeated schema content.

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 zero-parameter read with an output schema present, the description is complete: it defines what the tool returns at a high level, warns about token identity semantics, states required inputs, and gives an invocation example. Nothing needed to call or interpret the tool correctly is missing.

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?

This is a zero-parameter tool, so the baseline is 4 per the rubric. The input schema fully covers the argument surface, and the description reinforces it with 'REQUIRED: nothing' and the example 'setup_get_status({})'.

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 uses a specific verb, 'Read', and names the resource, 'current TikTok-side setup state', along with concrete contents such as connection email, advertiser counts, and auto-pull cadence. It does not explicitly contrast with sibling setup status tools, like setup_check_channel_connect or tiktok_get_assets_status, so it misses the strongest sibling differentiation.

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 intended use is clear: call it to read the authenticated user's TikTok-side setup state, and it adds an important interpretation step for the connection.email value. It does not state exclusions or alternative sibling tools, but for a zero-parameter read with no prerequisites, the context is sufficient.

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