tiktok_get_spark_organic_joins

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does state 'Read-only only' and notes that organic endpoints are attempted conditionally on permissions, which are useful disclosures. However, it omits failure modes, return behavior, and what happens when optional endpoints are unavailable, leaving significant 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?

The description is two short sentences, both informative: the core join action and the read-only guarantee. There is no filler or repetition. While it is terse, the efficient structure front-loads the primary purpose and a key behavioral constraint.

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?

With no output schema and no annotations, the description needs to explain what the tool returns and when to apply it, but it does not. It also does not address the behavior of optional experimental endpoints, which are relevant because includeExperimentalEndpoints can return 404. Given the tool's complexity (8 parameters, 1 required), this is a significant completeness 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 88%, and most parameters already have clear descriptions in the schema. The tool description itself adds no parameter-level detail, only framing the overall join operation. A baseline score of 3 is appropriate because the schema does the heavy lifting for parameter meaning.

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 a specific verb ('Join') and names the resources involved: Spark Ads fields, paid page/post reporting, and optional organic identity/post endpoints. It clearly conveys a data-merging purpose, though it doesn't explicitly distinguish this from sibling tiktok_get_spark_ads. The 'Read-only only' qualifier adds a precise behavioral boundary.

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 siblings like tiktok_get_spark_ads or tiktok_get_ads. The mention of 'when permissions allow' hints at conditional availability but does not state prerequisites, use-case criteria, or exclusions. An agent would have to infer the appropriate context from the name and parameter schema.

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