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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description is not required to restate safety. However, it adds almost nothing beyond them: it does not clarify what 'actual' connected destinations means, whether results are brand-scoped, or how pagination behaves given the limit/cursor parameters.

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?

A single front-loaded sentence with no wasted wording. It is efficient, though its brevity comes at the cost of substance rather than being paired with useful detail.

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?

An output schema exists, so return values need not be described. But for a paginated, brand-scoped list tool with 0% parameter coverage, the description omits required arguments, pagination behavior, and sibling routing — leaving real gaps an agent must guess at.

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% across three parameters, including the required brandId scoping key and the limit/cursor pagination pair. The description mentions none of them, so it fails to compensate for the complete absence of parameter documentation.

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 verb 'List' plus resource 'connected destinations and publishing capabilities' gives a rough idea of scope, but 'actual' is unexplained and the tool is not distinguished from nearby siblings such as get_channel_connection, connect_channel, or select_channel_accounts. An agent cannot tell from this sentence whether it returns accounts, capabilities, or both.

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 guidance on when to call this versus connect_channel, get_channel_connection, or select_channel_accounts, nor any statement of prerequisites. Usage must be inferred entirely from the name.

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