tiktok_get_read_endpoint

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

With no annotations, the description carries the full burden of behavioral disclosure. It does well by stating that only GET requests are allowed, that relative v1.3 paths and JSON-compatible query parameters are validated, and that several risky categories are blocked. It does not mention error behavior or response format, but the main safety-relevant behaviors are transparently disclosed.

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 only two sentences and front-loads the core purpose and key behavioral constraints. It is efficient and well structured, though the word 'Advanced' adds little and could be removed without losing meaning.

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 generic escape-hatch tool with two parameters and no output schema, this description is reasonably complete. It tells the agent when to use the tool, what constraints apply, and what is blocked. The absence of explicit guidance on response shape or error handling is a minor gap given the raw-endpoint nature of the tool.

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 50%, with the endpoint parameter documented but the parameters object undocumented. The description adds useful meaning by explaining that endpoints are relative v1.3 paths and that parameters are treated as JSON-compatible query parameters. However, it does not fully compensate for the undocumented parameters object, leaving room for ambiguity about how nested or complex parameter values are handled.

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 this as a GET-only escape hatch for TikTok Business API read endpoints not covered by specialized MCP tools. It names the verb, resource, and precise scope, and the phrase 'not yet modeled by a specialized MCP tool' distinguishes it from the many sibling tools.

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 explicitly states when to use it: for documented JSON read endpoints that do not yet have a specialized MCP tool. It also states what is blocked (OAuth, mutations, downloads, lead-record paths), giving clear exclusions. However, it does not name a specific alternative tool to use instead, so it falls slightly short of the strongest possible guidance.

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