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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context about the analysis dimensions and engagement comparison, but it does not disclose account prerequisites, limitations, or return format. For a read-only analytics tool with annotations present, this is adequate but not rich 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 two tight sentences with no wasted wording. The purpose and breakdown dimensions are front-loaded, followed immediately by concrete usage scenarios.

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 single-parameter, read-only analytics tool with no output schema, the description gives enough context to understand what is analyzed and when to invoke it. It could be slightly more complete by noting any account connection requirements or summarized return shape, but the core selection information is present.

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?

There is only one parameter, username, and the schema description coverage is 100% with clear guidance that it should be provided without '@'. The description adds no parameter-specific meaning beyond what the schema already states, which is acceptable given the high coverage.

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: analyze TikTok content performance. It also names the breakdown dimensions (format, sponsorship, duration) and the engagement outcome, making the tool's purpose clear. However, it does not explicitly distinguish itself from similar siblings such as get_content_breakdown or get_tiktok_video_analytics.

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 second sentence gives clear use cases: questions about which TikTok content type works best, what videos to focus on, or content strategy recommendations. It does not mention when not to use the tool or name an alternative, so it falls short of full when/when-not guidance.

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