threads_get_post_insights

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing beyond the metric list. It omits that insights typically require ownership/admin authorization, whether unavailable metrics are omitted or zeroed, and any rate-limit or freshness caveats.

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?

A single front-loaded sentence of roughly 120 characters with no filler; the resource and the returned metrics are both stated up front.

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 two-parameter read tool with full schema coverage and no output schema, the description is adequate to call it, but it leaves out the authorization requirement and response-shape expectations (e.g. what happens when a metric is unavailable) that matter for a token-scoped analytics endpoint.

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 both post_id and the metric string (including its default) are already documented in the schema. The parenthetical metric list in the description mirrors that default rather than adding format or constraint detail, so baseline 3 applies.

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 (get insights/analytics) and resource (a specific Threads post), and enumerates the metrics returned. This is enough to separate it from threads_get_post (post content) and threads_get_user_insights (account-level), though it never names those siblings explicitly.

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 only implied by the phrase 'for a specific Threads post' — an agent can infer this is the per-post analytics call, but the description never states when to prefer it over threads_get_user_insights or threads_get_post, nor any prerequisite such as being the post author.

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