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

Annotations already declare a safe, idempotent, closed-world read, so the description's real contribution is provenance semantics: it warns that inaccessible or unverified source status stays explicit and that no private platform data is returned. That is meaningful context an agent cannot infer from the hints, though return format and freshness handling remain unstated.

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 with the content scope front-loaded and the provenance caveat second. No filler, though the first sentence is dense enough that it borders on a list-dump.

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, the description usefully characterizes what comes back (dated evidence plus editorially labelled checks) and its trust posture. The main remaining gap is the default/'all' behaviour and any shape of the returned data, which is minor for a single-parameter read 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?

The description enumerates the six platforms matching the enum values, which is helpful, but the schema has 0% description coverage and the description omits the 'all' option and never states that the parameter is optional. It adds value over the bare enum but does not fully compensate.

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 concrete verb ('Read') and a specific resource: dated official-source evidence plus separately labelled editorial checks across six named Chinese platforms. That content profile clearly separates it from siblings like evaluate_video_publish and search_manju, though the description never plainly says it retrieves 'platform rules' and leans on the name for that framing.

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 when-to-use guidance, no stated prerequisites, and no reference to any alternative tool. The six-platform coverage hints at scope but nothing tells an agent when this tool is the right choice versus evaluate_video_publish.

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