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

Annotations are absent, so the description carries the full burden. It does not disclose whether the operation is read-only, any error scenarios, authentication requirements, or side effects. The only additional information is billing and group metadata, which are not behavioral traits.

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 two short sentences: the first states the core action, and the second adds metadata. It is front-loaded and every word serves a purpose, with no redundancy or fluff.

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?

The tool is simple with one parameter and no output schema. The description is minimal and functional, but it does not specify what 'profile details' includes, which could be important for an agent to know if the return meets its needs. Given the lack of output schema, more specificity would improve completeness.

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% for the single parameter 'url', which includes a description and example. The description also repeats the URL context. With full schema coverage, the baseline of 3 is appropriate; description adds no significant extra meaning 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 states 'Retrieves the profile details for a given TikTok user URL', which clearly identifies the action (retrieve), the resource (profile details), and the input (TikTok user URL). It distinguishes from sibling tools like get_tiktok_v3_post_details by specifying 'user' and the platform 'TikTok'.

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 description implies usage when you have a TikTok user URL, but it does not explicitly mention when not to use it or reference alternative tools. It provides clear context for the intended scenario but lacks exclusions or guidance on choosing between similar tools.

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