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

The description goes well beyond the annotations by disclosing credit cost, cache-vs-live behavior, and that repeat requests may re-purchase data — all useful. But the cost statements conflict with each other ('at least 10 Nexscope credits' vs '1 credit per request'), which undermines the agent's ability to reason about expense; the read-only, non-destructive nature is already covered by annotations.

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 useful field list and cost caveat are buried among pasted documentation artifacts, including a duplicated cache paragraph that appears identically in the schema and a garbled fragment 'Threads Profile API View Pricing Get Threads profile info 1 credit per request'. The pricing contradiction also forces the reader to reconcile conflicting numbers.

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?

The field enumeration compensates reasonably for the absent output schema, and caching/cost behavior is present. Missing: what happens for nonexistent, private, or suspended accounts, handle format expectations, and any note on whether the response is a single object versus a collection.

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 baseline is 3. The description adds no new meaning for 'handle' (e.g. whether an @ prefix or URL is accepted) and merely repeats the cache_max_age paragraph verbatim from the schema, which is duplication rather than added semantics.

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 first sentence gives a specific verb and resource ('Retrieves a Threads user's public profile') and enumerates the returned fields, so an agent knows exactly what it gets. It does not, however, differentiate itself from neighbors like social_threads_search_users or social_threads_user_posts.

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 only implied: the agent must infer it should call this when it already has a handle and wants profile attributes rather than posts or search results. No explicit when-to-use, when-not, or alternative routing is stated, and the caching tradeoff guidance is copied from the schema rather than framed as a decision rule.

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