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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether disconnected/unavailable platforms appear, whether per-platform status or account identity is included, or whether any auth is needed to enumerate connections.

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 short, front-loaded sentence with zero filler. The only cost is that the terseness is achieved by dropping the verb and any operational detail rather than by tight writing.

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?

There is no output schema, so the description carries the burden of describing the return value — yet it never says whether the result is a bare name list, objects with connection status, or account identifiers. For a tool an agent would likely use as a routing step, that omission is significant despite the simple, fully documented input.

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 100% and the single project_id property is fully documented, including its source (list_projects) and the default-workspace fallback. The description adds no further semantics, so the baseline 3 applies.

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 fragment 'Which platforms (Shopify, Gmail, X, TikTok...) are connected' identifies the resource (connected platform integrations) and the examples narrow it usefully, distinguishing it from the many list_* siblings that enumerate other entities. But it is phrased as a question and largely restates the title 'List connected platforms' rather than stating a verb+resource 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?

No when-to-use guidance, no prerequisites, and no mention of how it relates to switch_project or the many list_* siblings. An agent must infer that this is the discovery step before calling platform-specific tools like shopify_list_orders.

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