threads_get_user_insights

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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to cover safety. However, it adds no behavioral context beyond what's in the schema (e.g., no mention of data availability, rate limits, or pagination). The claim 'Requires period parameter' is slightly inaccurate as period is optional with a default.

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 sentence with a parenthetical list, which is concise and front-loaded. However, it could be more precise about the period parameter's role (e.g., 'day for time-series, lifetime for demographics').

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?

Given no output schema, the description does not explain the return format or structure. It also omits guidance on how period affects results (time-series vs demographics). Annotations help, but the description is insufficient for a complex insights 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 coverage is 100%, so baseline is 3. The description adds value by listing the comma-separated metrics (views, likes, replies, etc.) in natural language, which helps the agent understand the metric parameter options without reading 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 clearly states the action (Get), the resource (account-level Threads insights), and lists the specific metrics. It distinguishes itself from sibling tools like threads_get_post_insights and ig_get_account_insights by specifying 'account-level' and 'Threads'.

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 description mentions 'Requires period parameter' but provides no guidance on when to use this tool versus alternatives (e.g., post-level insights or Instagram insights). It does not explain when 'day' vs 'lifetime' is appropriate, nor does it note that this is for the authenticated user's own account.

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