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

Annotations already mark this as a read-only open-world operation. The description adds useful behavioral context: results are public, ordered as the profile shows them, include like/reply/repost counts, support cursor pagination, and cost 1 credit. It does not cover auth or error behavior, but the added cost and pagination context is significant.

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 short and front-loaded with the core purpose, then pagination and cost details. The opening fragment 'User posts.' is slightly redundant with the title, but overall there is little wasted text.

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?

With no output schema and limited annotations, the description still gives an agent enough to call the tool: it identifies the returned post type, ordering, engagement counts, pagination mechanism, and credit cost. The main remaining gap is cache_max_age semantics.

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 67%, with cursor and handle documented in the schema. The description clarifies that pagination.cursor should be passed back as cursor for the next page, but it does not add meaning for cache_max_age or expand on handle formats.

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 states a specific resource and scope: public posts from a Threads profile, in profile display order, with engagement counts. It is clearly not a single-post or profile tool, though it does not explicitly name sibling alternatives.

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 explains what the tool returns but gives no explicit when-to-use guidance versus siblings such as threads_profile, threads_post, or threads_searchUsers. It also does not state prerequisites or exclusions.

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