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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the field-level return scope and the create_post dependency, but does not disclose any other behavioral details such as authorization requirements or potential errors. This is acceptable but not exceptional given the read-only annotation.

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 two sentences, front-loaded with the core return information and followed by a concise usage instruction. Every sentence provides distinct value and there is no filler or redundant wording.

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 one-parameter read-only tool, the description covers what the tool returns and when to call it. The main gap is that it does not specify where accountId comes from or link it to list_connected_accounts, which is relevant for an agent assembling a create_post workflow. Without an output schema, the listed fields help, but the parameter provenance remains under-specified.

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 schema has 0% description coverage for the single required accountId parameter. The description only says 'for an account,' which largely restates the parameter name and does not explain how to obtain the accountId or what format is expected. Since schema coverage is low, the description needs to compensate but only adds minimal meaning.

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 states a specific verb and resource: it returns TikTok creator fields such as nickname, avatar, privacy_level_options, interaction settings, max video duration, and posting limits. This clearly distinguishes it from sibling tools that handle posts or analytics. The tool name and description align without tautology.

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 says 'Use before create_post with tiktokTargets,' giving a concrete integration point and a clear when-to-use context. It does not formally list alternatives or when-not-to-use scenarios, so it doesn't quite earn a 5, but the guidance is actionable and clear.

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