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

The annotations already establish read-only, non-destructive, open-world behavior, and the description adds useful context: it renders an interactive dashboard, includes a daily trend and per-campaign table, defaults to the last 30 days, and reports amounts in the account currency. It does not cover data freshness or authorization requirements, but the annotations carry the safety profile.

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 front-loaded with the dashboard’s contents and metrics, then moves to rendering behavior, default period and currency. It is dense but every sentence contributes; no significant padding 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 seven-parameter, output-schema-less dashboard tool, the description explains the return shape (interactive dashboard with trend and campaign table), the reporting expectation, defaults and currency. It is close to complete, though it could add one line distinguishing this from related TikTok reporting tools.

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%, so all seven parameters including the detail enum, date presets, account and folder fields are already documented. The description only reinforces the default date range and currency, adding little parameter meaning beyond the schema.

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 names the specific resource (TikTok Ads performance dashboard) and lists the exact metrics returned: spend, results, cost per result, clicks, CTR, CPC, purchases, purchase value, ROAS, trend and per-campaign table. It is clearly a performance-reporting tool, but it does not explicitly distinguish itself from siblings like tiktok_report_query or tiktok_breakdown.

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?

Usage is implied: it is a dashboard for performance overviews, defaults to the last 30 days, and the agent should summarise the main findings. There is no explicit guidance on when to choose it over tiktok_report_query or a breakdown tool, which leaves the routing decision partly to inference.

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