threads_get_media_insights

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get', which implies a read operation, but does not mention permissions, ownership requirements, rate limits, or what happens if the media_id is invalid. This minimal transparency is insufficient given the lack of annotations.

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 very concise and front-loads the purpose. However, it includes a 'ctx' parameter in the Args section that is not present in the input schema, which could mislead the agent. This minor structural flaw prevents a perfect score, but overall it is compact and well-organized.

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 the tool's low complexity (single parameter, output schema present), the description is minimally adequate. It states the core purpose and identifies the required parameter. However, it lacks usage guidelines, behavioral context, and parameter semantics beyond the schema, leaving some gaps in completeness.

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 0%, so the description must compensate. However, it only states 'The ID of the media/post to get insights for', which essentially restates the parameter name and adds no new semantics (e.g., format, required vs optional, or validation). The parameter name 'media_id' is already self-explanatory.

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 tool retrieves metrics/insights for a specific post, using the specific verb 'Get' and identifying the resource ('a specific post'). This distinguishes it from sibling tools like threads_get_user_insights (user-level) and threads_get_post (post details).

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states what the tool does without contextualizing when it should be selected over threads_get_user_insights or other post-related tools.

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