Read one mention from the TikTok mentions webhook

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

Annotations already cover readOnlyHint and destructiveHint, so the description's addition of the 48-hour data retention, auth requirement ('NEEDS THE TIKTOK ACCOUNT AUTHORIZATION with the brand-insights permission'), and the fact it's free and read-only adds meaningful behavioral context beyond annotations. No contradiction.

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 a single paragraph but dense with critical info: purpose, use case, urgency (48h), alternative, param requirement, and auth. Every sentence adds value, and the key constraint (48h) is front-loaded. Slightly long but justified by the number of important caveats.

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 tool with 3 params, no output schema, and existing annotations, the description covers purpose, usage context, data availability, alternatives, auth, and read-only nature. An agent has all necessary information to decide when to call this and what to expect.

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 the baseline applies. The description reiterates itemId is required even for comments and that commentId selects comments, but the schema already explains this. No additional semantic value beyond what's in 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 states a specific verb ('Read the full detail of a SINGLE mention'), identifies the resource (TikTok mention), and distinguishes post vs comment via commentId. It also contrasts with sibling tools (list_tiktok_mentions, list_tiktok_mention_comments) by noting it serves the webhook use case, making it easy to differentiate.

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 states when to use (webhook events with only ids) and when not (anything older than 48 hours, pointing to list_tiktok_mentions or list_tiktok_mention_comments). Also clarifies itemId is required even for comments, and mentions the 48-hour data guarantee as a critical constraint.

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