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

With no annotations, the description carries the full burden; it usefully discloses the local database source, the fuzzy ILIKE matching behavior, and a prompt-injection warning about returned content being untrusted. It omits auth requirements, result ordering, pagination, and behavior on zero matches, so the disclosure is partial.

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?

A single compact sentence with the core purpose front-loaded and the trust warning appended. No filler, though the parenthetical technical detail slightly crowds the main clause.

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 2-parameter list tool with no output schema and no annotations, the description covers matching semantics and a safety caveat but leaves the return shape, ordering, and sibling-tool choice unaddressed. Adequate but with clear gaps.

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% and both parameters are documented in the schema (limit range 1-100, query as unique_id or nickname). The description restates the same field semantics without adding syntax, matching-operator, or escaping details, so the baseline 3 applies.

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?

States a specific verb and resource ('Search TikTok users by unique_id or nickname') and adds the matching mechanism (pg_trgm ILIKE over a local database). It does not differentiate itself from close siblings like search_users or get_tt_user_by_username, so an agent must infer which is authoritative.

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?

No explicit guidance on when to choose this over the many sibling search/lookup tools (search_users, get_tt_user_by_username, get_users_by_ids). The 'search' framing implies lookup usage but no conditions, alternatives, or exclusions are given.

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