list_platforms

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that results include the accepted tags and levels per platform, which is behavioral context not in the annotations, but it says nothing about result size or freshness.

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?

One compact sentence with the key content front-loaded; nothing is padded. It is a fragment rather than a full sentence, which slightly weakens clarity but costs no length.

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 parameters, an output schema present to describe return values, and annotations covering the read-only/open-world profile, the description needs only to say what is listed and why. It does that, though the missing usage cue leaves a small 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?

The tool takes zero parameters, so by baseline this scores 4. The description correctly implies no input is needed to enumerate platforms.

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 resource is clearly identified ('connected platforms') and the description adds what each entry carries (tags and levels usable as filters), which distinguishes it from all siblings. However, it is a noun phrase with no verb, so the agent must infer that this is a listing/retrieval operation rather than, say, a capability probe.

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 call this versus alternatives, and no prerequisites. The phrase 'accepts as filters' hints the output is meant to bootstrap other filter-based calls, but that routing advice is never made explicit.

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