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

The description explicitly notes 'read-only MCP surface,' which signals a non-destructive operation, and 'cached' implies data may be stale. Since no annotations are present, the description carries the full disclosure burden. However, it does not describe the response format, pagination behavior, or whether filters like date ranges affect the cached data, leaving significant behavior unexplained.

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, front-loaded sentence with no filler. It efficiently communicates the core function and read-only nature, making every word contribute. This is appropriately concise.

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 8 parameters, no parameter explanations, no usage guidelines, and no output schema, this description is incomplete. An agent would not know the return shape, how caching interacts with filters, or what results to expect. It only covers the top-level purpose.

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?

With 8 parameters and 0% schema description coverage, the description must compensate, but it explains none of the parameters. It does not clarify what 'page', 'search', 'group_by', 'sort_dir', 'sort_key', 'date_from', 'date_to', or 'page_size' mean in the context of the overview. An agent has no semantic anchor for these inputs.

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 and resource: 'read the authenticated tenant's cached TikTok insight overview.' It clearly indicates a read operation on cached data, and the phrase 'read-only MCP surface' reinforces this. However, it does not explicitly distinguish it from sibling insight tools like insights_query_overview or insights_pull_insights, so an agent must infer which to choose based on the 'cached' qualifier.

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?

No guidance is provided about when to use this tool versus the numerous insight-related siblings. The description does not mention prerequisites, cache-freshness expectations, or scenarios where this tool is preferred over others. An agent is left to guess based on the tool name.

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