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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds genuinely useful behavior: a hard cap of 10 results per request due to public API limits, credit consumption, and the warning that repeated requests may re-purchase the same data. The only deduction is the muddled pricing block, which states both 'at least 10 Nexscope credits' and '1 credit per request', leaving cost ambiguous.

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 core capability and return fields are front-loaded in a strong first sentence, and the 10-result limit is stated twice (once mid-text, once in the appended marketing block). The pasted pricing/landing-page copy ('View Pricing Search public Threads posts...', 'Examples are not guaranteed prices') is boilerplate that dilutes the signal.

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?

For a read-only search with no output schema, listing the returned fields and the 10-result ceiling covers most of what an agent needs. However, with no pagination or cursor mechanism to exceed 10 results, and no date-format guidance for the date filters, an agent could reasonably call it in a way that returns fewer or misparsed results than intended.

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 all four parameters are already documented in the schema, and the description adds no extra syntax — notably it never gives a date format for start_date/end_date or clarifies how 'trim' shortens the response. Baseline 3 is appropriate when the schema carries the 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?

Opening sentence gives a specific verb (searches), an explicit resource (Threads posts), and the selection mechanism (keyword), and it enumerates the returned fields so the agent knows exactly what payload to expect. Against siblings like social_threads_search_users and social_threads_user_posts, the 'posts matching a keyword' framing is enough to distinguish it without opening a schema.

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?

It hints at iterative use ('Repeat searches over time to find new results') and implies keyword-driven discovery, but never states when to prefer this over social_threads_search_users or social_threads_user_posts, nor any preconditions. Usage is inferable rather than spelled out.

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