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

With no annotations, the description carries the full behavioral disclosure burden. It adds value by explicitly stating the redaction boundary: no internal issue URL, operator note, stack trace, provider response, or other tenant data. The verb 'Read' also implies a non-mutating operation, though this is not explicitly guaranteed.

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 with no filler. The main action and resource are front-loaded, and the negative scope is efficiently listed in a second sentence. Every word earns its place.

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 simple single-parameter read tool, the description gives the core purpose and safety boundary, but leaves important gaps: possible status values, how to obtain report_ref, and error/not-found behavior. Since there is no output schema, the description could better describe what 'state' looks like in the response.

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 coverage is 0% for the only parameter, report_ref. The description mentions 'one tenant-owned TikTok support report' but does not define what report_ref is, how it should be formatted, where it comes from, or whether it is an ID, string, or reference. The parameter name alone is insufficient for an agent to construct a valid call.

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 states a specific verb ('Read'), a specific resource ('customer-safe state of one tenant-owned TikTok support report'), and reinforces scope by listing what is intentionally excluded. It is clearly distinguishable from siblings like support_report_error, which suggests creating/reporting an error, whereas this reads status.

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?

No guidance is provided about when to use this tool versus alternatives such as support_report_error, operations_get, or tasks_get_status. The description does not mention prerequisites like how a report_ref is obtained or when a status check is appropriate rather than other operations.

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