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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely new behavior by naming the response fields and disclosing cost implications, including that repeated requests may re-purchase the same data. That cost/caching caveat is exactly the kind of thing annotations cannot convey.

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 purpose is front-loaded well, but roughly half the text is pasted pricing boilerplate that repeats itself ("at least 10 Nexscope credits" versus "1 credit per request") and ends with a disclaimer about examples. This internal inconsistency and duplication make the definition noisier than it needs to be.

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 one-parameter read tool with no output schema, the description supplies the returned field list and the cost behavior, which is enough for an agent to call it confidently. The only gap is the unresolved pricing contradiction, which leaves the actual credit cost ambiguous.

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 the single 'query' parameter is already documented as "Username to search for." The description's phrase "by username" reinforces that this is not a free-text keyword search, but it adds no syntax, matching behavior, or result-limit detail 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 first sentence states a specific verb and resource (searches Threads users by username) and enumerates the returned fields (username, full_name, profile_pic_url, is_verified, pk). It is clearly distinguishable from siblings like social_threads_profile or social_threads_user_posts, which it implicitly points to as the next step.

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?

"Useful for finding user accounts before fetching their profile or posts" gives a concrete workflow context that routes the agent toward the profile/posts siblings afterward. It stops short of explicitly naming those sibling tools or stating when NOT to call this, so it is strong context rather than full when/when-not guidance.

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