list_tiktok_accounts

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

With no annotations, the description carries full burden for behavioral disclosure. It only mentions 'List' and 'connected via OAuth,' but does not explain whether this is a read-only operation, whether there are any side effects, how results are paginated, or what data is returned. This is a significant gap for a tool listing accounts.

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 one short sentence that communicates the core purpose without wasted words. It is appropriately sized for a zero-parameter tool.

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?

While the description is clear and concise, it lacks any mention of return format, potential limitations, or the meaning of 'connected via OAuth.' Given the absence of an output schema and annotations, the description could be slightly more informative, but for a simple list operation it is minimally adequate.

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?

The tool has zero parameters, and the input schema confirms an empty object. The description adds no parameter details, but none are needed; the baseline score of 4 applies because there is nothing to explain.

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 uses the specific verb 'List' and names the resource 'TikTok accounts connected via OAuth.' This clearly distinguishes it from sibling tools like list_tiktok_posts and get_account, which target different resources or operations.

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 provides no information about when to use this tool, what prerequisites exist, or how it differs from alternatives. It neither states exclusions nor suggests alternative tools, leaving the agent without guidance on tool selection.

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