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

With no annotations, the description carries the full burden, and it does add two real facts: the data comes from a local database (not live API) and returned content is user-generated and untrusted. It says nothing about auth requirements, rate limits, pagination, or what happens on a miss, which for a lookup tool with zero annotation coverage leaves gaps.

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?

Two tight sentences: the lookup contract first, the safety caveat second. Every clause earns its place with no redundant restatement of the tool name.

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 single-parameter, no-output-schema lookup the description is serviceable, giving source and trust level. It stops short of describing what fields the profile contains or the failure behavior, so an agent knows how to call it but not quite what it will get back.

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?

Only one parameter and schema description coverage is 100%, so the schema already explains the handle format including 'without @'. The description's restatement of 'unique_id (TikTok handle)' adds no syntax or edge-case detail beyond the schema, so 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 (Get) and resource (TikTok user profile) plus the keying identifier (unique_id/handle). The 'TikTok' qualifier and 'by_username' framing separate it from the many other get_* siblings, though it never explicitly names get_tt_user_by_id or search_tt_users as the alternatives.

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?

Usage is implied by the input contract: look up a single user when you have the handle rather than the numeric ID. No explicit when-to-use, when-not-to-use, or alternative routing (e.g., 'use search_tt_users for partial matches') is given.

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