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

Annotations already declare readOnlyHint=true, so the safety profile is covered structurally. The description adds genuine behavioral context by disclosing what is deliberately withheld from the payload (internal issue URL, operator notes, stack traces, provider responses), which tells the agent what it will NOT be able to inspect.

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 tight sentences, both front-loaded and free of filler. The redaction clause earns its place given the absence of an output schema, though the description still leaves the positive return shape unstated.

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 read tool with no output schema, an agent would benefit from knowing the possible state values, not just what is redacted. The privacy guarantee is well covered, but the actual returned content is only described as 'customer-safe state', leaving a noticeable 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 0% for two parameters, so the description must carry the burden of explaining them. It implies report_ref selects a single tenant-owned report but gives no syntax or format, and it never mentions the connection_context parameter at all.

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 gives a specific verb (Read) and resource (the state of one tenant-owned TikTok support report), making the intent unambiguous. It reads clearly against a catalog of many unrelated siblings, though it never names the natural counterpart support_report_error to sharpen the 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 statement of when to reach for this tool versus support_report_error or any other status reader. Usage is only implicit from 'read the state of one report'; no prerequisites, no exclusions, and no routing guidance are offered.

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