get_post_analytics

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

No annotations are provided, so the description carries the burden. It discloses the return shape (JSON string), the metrics included, and mentions raw data. It does not cover error behavior, rate limits, or auth requirements, but for a simple read/fetch operation this is reasonably transparent.

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 compact and front-loaded, with clear Args and Returns sections. It slightly repeats the metric list in both the summary and the return description, but overall it is well-structured and economical.

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 single-parameter read tool with return information included, this description is largely complete. It explains what the tool does, what parameter is required, and what the caller should expect back. It lacks explicit alternative routing, but that is not essential to invoking it correctly.

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. It does define media_id as a 'Unique Threads post/media ID', which adds domain meaning beyond the bare schema, but it offers no example or format guidance.

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 uses a specific verb ('Fetch') and resource ('engagement analytics for a specific post'), and lists the exact metrics returned. This clearly distinguishes it from account-level analytics and post-details 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 phrase 'for a specific post' gives clear context for when to use this tool, implicitly separating it from get_account_analytics. However, it does not explicitly name alternatives or state when not to use them.

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