social_media_posting_get_tiktok_business_profile

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which covers safety. The description adds no behavioral context beyond that—no mention of auth requirements, response format, or what happens if the account isn't a business account. It is consistent with the annotations but contributes nothing extra.

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 single short sentence, which is efficient and front-loaded, but it is also essentially a restatement of the tool name without added nuance. It earns its place, but just barely; there is no elaboration to structure.

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 get tool, the description omits critical context: what information the profile contains, whether a business account must be connected, or how the result should be used. While the annotations cover safety, the lack of usage context and the existence of a sibling tool make this incomplete for an agent to reliably select and execute it.

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%, with each parameter having a brief but functional description. The tool description adds no parameter-level detail, so the baseline of 3 applies. The schema's 'Defaults to GHL_LOCATION_ID when omitted' is helpful, but it comes from the schema, not the description.

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 verb 'Get' and the resource 'Tiktok Business profile'. However, it fails to distinguish this tool from the nearly identical sibling social_media_posting_get_tiktok_profile, so an agent might not know which profile variant to use without additional context.

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 gives no guidance on when to use this tool versus the non-business TikTok profile getter, nor does it mention any prerequisites like having a connected business account. No alternatives are named or excluded.

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