social_media_posting_get_tiktok_profile

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds no extra behavioral detail such as what data is returned, any authentication requirements, or what happens if the profile doesn't exist. It essentially restates the tool's name without enriching the agent's understanding beyond the annotations.

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 a concise single sentence with no wasted words. It is appropriately sized for a simple read operation and front-loads the core action and resource. While it could include more detail, it does not suffer from verbosity or irrelevant content.

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?

Given the tool's simplicity and the absence of an output schema, the description should clarify what the returned profile data contains and differentiate it from the sibling business profile tool. It fails to explain the purpose of accountId and locationId beyond the schema, and does not mention any prerequisites or typical use cases. The lack of context makes it incomplete for agents choosing between related profile-fetching tools.

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 input schema has 100% description coverage for both parameters (accountId and locationId), so the schema already explains their meanings. The description adds no additional context about parameter usage, defaults, or how they relate to the profile retrieval. Baseline of 3 is appropriate given the schema's completeness.

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 states the action (get) and resource (TikTok profile), making it unambiguous what the tool does. It distinguishes from other social media tools by specifying TikTok, but it does not explicitly differentiate from its sibling 'social_media_posting_get_tiktok_business_profile', which is a closely related tool that could cause confusion.

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?

There is no guidance on when to use this tool versus alternatives such as the TikTok business profile variant or attach/oauth tools. It does not mention prerequisites like having an existing accountId or any setup steps. The description provides no context for selecting this tool over others in the same family.

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