creator_info

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

With no annotations, the description carries full burden and succeeds: it discloses that the endpoint is Direct-Post-only, gated on video.publish, unavailable in upload mode, and automatically consulted to avoid rejected posts due to unsupported privacy_level. It also lists the returned fields, providing strong behavioral context.

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 description is compact and front-loaded: a scannable list of returned fields followed by two sentences of critical context. No filler or repetition.

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, no-output-schema info tool, the description covers what the tool returns (nickname, privacy levels, duration cap, interaction toggles), when it runs, and why it is needed. It leaves no major gaps for a pre-post lookup.

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?

The tool has zero parameters, so there is nothing for the schema to describe; the description confirms it is a no-input lookup of fixed creator properties. Baseline 4 is appropriate because no parameter explanation is needed.

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 opens with the data the tool exposes ('Nickname, allowed privacy levels, duration cap, interaction toggles'), making it clear this is a creator-info lookup, and later explains its role before direct posts. It lacks an explicit verb like 'retrieves' or 'returns,' so it falls just short of the strongest purpose statement, but it is unmistakably distinct from sibling tools.

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 explicitly states when to use it ('Consulted automatically before a direct post'), when not ('unavailable — and unnecessary — in upload mode'), and explains the underlying TikTok permission gating on video.publish. It gives clear context with no need for alternative tool mentions.

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