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

Beyond the readOnly/openWorld annotations, the description discloses key behavior: results come from threads.net via a residential proxy, ranking is controlled by Threads, there is no date filter, typical result counts are 10-20, and billing occurs only on successful calls.

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 dense but front-loaded with the core purpose before adding operational details. Every sentence carries useful information, though the first sentence packs many clauses together.

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?

Given the output schema exists, the description need not explain return fields, but it still summarizes them. It also covers operational constraints, result variability, proxy source, and payment behavior, leaving little ambiguity for an agent invoking the tool.

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% and both parameters are documented in the schema. The description adds only indirect context such as typical result counts and lack of date filtering, without expanding on q syntax or limit semantics 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 gives a specific verb and resource: searching Threads (Meta) posts for a keyword or hashtag. It clearly scopes results to top posts as shown by the logged-out search page, distinguishing it from profile/reply-oriented Threads siblings.

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 clearly indicates the appropriate use case: keyword/hashtag post discovery on Threads. It also states important limits such as no date filter and Threads-controlled ranking, though it does not explicitly name sibling alternatives like social_threads_replies or social_threads_profile.

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