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

No annotations are provided, so the description carries the full behavioral burden. It clearly states a read-only listing action, which is transparent for a simple tool, but it does not mention ordering, locale, pagination, or whether platform identifiers are returned beyond display names. For a zero-parameter list operation, this is minimally viable but not richly transparent.

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 one concise sentence, front-loads the action and resource, and contains no unnecessary words. It is appropriately sized for a tool that takes no parameters and has a simple purpose.

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 zero-parameter tool with no output schema, the description adequately communicates what will be returned: supported platforms and their display names. It could have been slightly more explicit about the exact return shape (e.g., whether platform codes are included), but the description is otherwise complete for safe invocation.

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 tool has zero parameters and the schema properties object is empty, so there is nothing for the description to add about parameter behavior. The baseline of 4 applies, and the description's statement about listing all platforms without requiring input is consistent with this.

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 names a clear verb ('List') and resource ('supported platforms'), and specifies the output content ('their display names'). This makes the tool's purpose immediately understandable and distinguishes it from the sibling query_hot_trending, which is clearly a different kind of operation.

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 implies when the tool is useful: whenever an agent needs to know which platforms are supported and what their display names are. However, it does not explicitly explain when to prefer this over query_hot_trending or mention any alternative usage path, so the guidance remains implicit rather than explicit.

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