threads_get_user_insights

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

No annotations exist, so the description carries full burden. It discloses the scope ('account-level') and lists metrics, but fails to mention rate limits, data freshness, required permissions, or response behavior. For a read tool, transparency is minimal.

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?

Single sentence, front-loaded with essential information. Could be slightly more efficient by omitting the period hint (already in schema), but overall it's concise and readable.

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?

No output schema exists, so the description should explain return shape or behavior. It omits critical constraints (e.g., since/until required when period is 'day', lifetime only for demographics) and does not describe the response format. Incomplete for a 4-parameter 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 the schema already describes each parameter. The description adds 'Requires period parameter', which is misleading because period is optional with a default in the schema. It does not clarify that since/until are required when period is 'day'.

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 'Get account-level Threads insights' with a specific verb (Get) and resource (account-level Threads insights). It lists example metrics, distinguishing it from siblings like threads_get_post_insights (post-level) and IG tools.

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 notes a requirement ('Requires period parameter'), but provides no explicit guidance on when to use this tool versus alternatives (e.g., threads_get_post_insights or IG account insights). No when-not or exclusion criteria are given.

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