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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, yet the description still adds real behavioral context: per-request credit cost, cache-hit behavior returning 'cached': true with zero credits, and what the trim option changes. One flaw: it says 'Completed lookups cost at least 10 Nexscope credits' and then '1 credit per request', an internal inconsistency that could mislead cost-sensitive planning.

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 opening sentence and the threadItems-versus-comments clarification are well front-loaded, but the tail is pasted documentation: 'Threads Post API View Pricing Get a post by url...' repeats what was just said, repeats the cache paragraph verbatim from the schema, and includes a raw markdown link. Roughly half the text is duplication.

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 correctly compensates by listing the returned fields (caption, like_count, view_counts, image_versions2, taken_at, comments, threadItems, relatedPosts). Cost and caching semantics are covered too; only the contradictory credit figures and lack of pagination/response-size guidance keep it from a 5.

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 100%, so url, trim and cache_max_age are already fully documented in the schema, and the description largely restates that text. It does add marginal meaning by explaining that caching avoids a live scrape and that trim yields a 'lighter' response, but no format or syntax detail beyond structured fields.

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?

States a specific verb and resource ('Fetches a single Threads post by URL') and enumerates the returned fields, so the agent knows exactly what it retrieves. The 'single post by URL' framing implicitly separates it from siblings like social_threads_user_posts and social_threads_search, though no sibling is named explicitly.

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 rather than stated: the agent learns it needs a post URL, and the cache_max_age section explains the cached-vs-live tradeoff. There is no explicit guidance on when to choose this over social_threads_user_posts or social_threads_search, nor any stated prerequisite for obtaining a valid post URL.

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