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

Annotations cover the safety profile, and the description goes well beyond them: it enumerates the returned fields per profile, notes next_cursor exists only on TikTok, and discloses pricing ($0.02 per successful call), the billing exclusions, and the x402/USDC-on-Base payment channel passed in _meta. That is exactly the operational context an agent cannot get from structured fields.

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?

Three dense sentences, front-loaded with what is searched and what comes back, with pricing and payment last. The field enumeration ('handle, name, bio, followers, following, posts and verification') is a bit list-heavy but is load-bearing since no output schema exists.

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 return fields, and it covers pagination and payment. What is left unstated is rate limiting, auth requirements outside of payment, and error behavior beyond the billing carve-outs, so it is strong but not exhaustive.

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 the baseline is 3. The description does add one piece of meaning beyond the schema by scoping cursor/next_cursor to TikTok ('next_cursor on TikTok'), but q and platform semantics are left entirely to 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?

Specific verb plus resource: 'search public TikTok, Instagram or Threads profiles by name or keyword', with an explicit scope qualifier ('unfiltered'). It distinguishes the tool as a cross-platform profile-level lookup, though it never names how it differs from siblings like social_search, tiktok_search, or instagram_profile, leaving some overlap to inference.

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?

The 'unfiltered' label and the title hint that filtered alternatives exist elsewhere, but the description never states when to choose this over the many sibling search tools or what a cursor requires. Usage is implied rather than spelled out; only the billing conditions (bad input free, not-found uncharged) are explicit.

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