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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered; the description adds that the output is an assembled multi-section report rather than raw data. It does not disclose latency/cost of analysis, whether data is fetched live, or how recommendations are produced, which is meaningful for a synthesis tool.

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?

Two sentences, front-loaded with the verb and resource, then the section inventory, then the trigger conditions. 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?

With no output schema, the description compensates by enumerating the report's sections, and the schema covers format/period/username fully. The remaining gap is sibling disambiguation against generate_report, which an agent would need to pick the right report tool.

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 description coverage is 100% with enums and defaults for 'format' and 'period', and a clear 'username (without @)' description, so the schema fully documents the inputs. The description adds no parameter-level meaning beyond that, which is the correct baseline 3 when the schema does the work.

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 ('Generate a comprehensive TikTok analytics report') and enumerates the sections it contains (executive summary, growth, engagement, top videos, recommendations). It is clearly a TikTok-scoped report builder rather than a raw data getter, so it separates from the get_tiktok_* siblings, though it never names the generic 'generate_report' sibling it most overlaps with.

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?

Explicitly lists trigger scenarios: 'TikTok report, performance review, client TikTok summary, or TikTok account audit', which gives an agent a clear use context. It offers no exclusions or routing guidance versus the generic generate_report or versus assembling the report from individual get_tiktok_* calls.

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