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

With no annotations provided, the description carries the full burden and does well by disclosing the credit cost, the free cache-hit path, the no-charge behavior for empty results and failures, and the always-fresh default. It also reveals result contents and the platform-matching constraint. It does not explicitly state that the operation is read-only or discuss rate limits, but the nature of the tool and the disclosed cost/cache behavior provide substantial transparency.

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-loads the core resource and fields, but it contains redundancy: 'Flat 2 credits' appears twice, and 'Costs 2 credits' repeats the same information. The fragment 'source + stages/ms' is cryptic and could be clearer. Worthy information is present, but the duplicate pricing statement is unnecessary.

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?

There is no output schema, so the description must communicate enough about the return value, and it does by listing engagement fields and thread metadata. It also covers pricing, cache behavior, failure charging, and platform restrictions. The main gap is that 'source + stages/ms' is undefined, and there is no mention of pagination beyond the limit parameter, but overall the description is adequate for invoking the tool 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?

The input schema has 100% parameter coverage, so the baseline is 3. The description adds no significant parameter meaning beyond the schema: the cache behavior and limit caveat are already fully documented in the schema property descriptions. The description's credit and result-field notes are valuable but not parameter-specific.

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 identifies the resource as 'Recent Threads posts' and lists the key returned fields (engagement metrics, threadId/isReply), which makes the tool's purpose clear. It lacks an explicit verb like 'list' or 'fetch' and does not directly say 'for a profile,' though the required url parameter clarifies that the target is a Threads profile or @handle. It is sufficiently distinct from siblings like threads_post_details, which targets a single post.

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 gives useful operational guidance, such as passing cache=true for a free cache hit, the flat credit cost, and the fact that limit cannot increase what Threads returns. However, it does not explicitly state when to choose this tool over alternatives like threads_post_details, threads_profile, or threads_search. Usage context is implied rather than stated with clear when-to-use or when-not-to-use conditions.

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