postifys_tiktok_creator_info

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

With no annotations, the description carries the full burden. The verb 'Fetch' strongly implies a read-only operation, and the parenthetical gives a sense of the response content. However, it doesn't mention potential errors, authentication requirements, or what happens if the account is invalid, leaving some typical 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 short sentences deliver the core purpose and the critical usage timing. The first sentence is front-loaded with the action and resource, and the second sentence provides actionable guidance with no wasted words.

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 tool with no output schema, the description is suitably complete: it states what data is fetched, points to the source of the input parameter, and specifies when to call it. The only minor omission is the exact response format, but the described content types partially fill that gap.

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 the only parameter tiktokAccountId is fully documented as coming from postifys_list_connections. The description adds no new parameter-level meaning, so the baseline of 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?

The description clearly identifies the verb 'Fetch' and the resource 'TikTok creator publish options', and specifies the content as 'privacy levels, interactions'. This goes well beyond the tool name and distinguishes it from siblings like postifys_publish and postifys_list_connections.

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 instruction 'Call before Direct Post' provides an explicit temporal usage context and implies a prerequisite relationship with the publish tool. It tells the agent when to invoke this tool, though it doesn't explicitly name alternatives or when not to use it.

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