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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description usefully discloses the shape of the returned data (privacy levels, disabled-feature flags, max length), but says nothing about auth requirements for the connected account or how to obtain a valid accountId.

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?

A single front-loaded sentence with the key scope ('TikTok creator info for a connected account') first, followed by the enumerated contents. The trailing parenthetical is mildly informational but not wasteful.

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 simple read-only, single-parameter lookup with annotations covering safety, the description supplies the important missing piece: what the return payload contains. It is close to complete, with only the accountId provenance unaddressed.

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?

With 1 parameter at 0% schema coverage, the schema documents the accountId field only as an untyped-format string. The description partially compensates by framing it as 'a connected account', but adds no format, source, or lookup guidance beyond that.

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: retrieves 'TikTok creator info for a connected account', and enumerates what that info contains (privacy levels, comment/duet/stitch flags, max video length). This is clearly a read/info tool, distinguishable from the creation and posting siblings, though it doesn't explicitly name an 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?

The phrase '(used by the composer UI)' implies this is fetched ahead of composing a TikTok post, which gives context. However, it never states when an agent should call it versus siblings like compose_post or create_post, nor any prerequisites beyond a 'connected account'.

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