Post

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

Annotations declare readOnlyHint=false, which could mislead an agent into assuming a write; the description usefully resolves this by stating these are 'read-like POST requests [that] do not publish to social platforms', and it adds real operational context: credit consumption and the confirm=true requirement. It stops short of describing failure modes, rate limits, or idempotency behavior, so not a 5.

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?

Purpose is front-loaded and the cost/confirm warning is appropriately placed at the end. The long inline enumeration of return fields (like_count, image_versions2, text_post_app_info, etc.) is verbose, though defensible given there is no output schema.

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, the description carries the return-value burden and does so by listing scalar fields plus the comments/threadItems/relatedPosts arrays, and it clarifies that threadItems (author continuations) differ from comments. Combined with the credit/confirm notes, this is nearly complete; only error and caching tradeoff behavior is left to the schema.

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 100%, so the schema already documents url, trim, account, confirm, and the cache_max_age enum; baseline is 3. The description reinforces trim ('lighter responses') and the credit rationale behind confirm, but adds no syntax or format meaning beyond the schema.

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 opens with a concrete verb+resource+scope: 'Fetches a single Threads post by URL', which lets an agent distinguish it from list-style siblings like threads_posts. It does not, however, explicitly name an alternative (threads_posts, threads_search_by_keyword) to route between, so it stays below the 'sibling differentiation' bar for a 5.

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 implied by the required url parameter (single-post retrieval) and by the note that trim yields lighter responses. There is no explicit when-to-use/when-not-to-use guidance or pointer to the sibling that lists a user's posts or searches by keyword, so an agent must infer the boundary between threads_post and threads_posts.

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