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

With no annotations, the description carries the full behavioral burden. It only provides a noun phrase about connected social accounts and plan coverage; it does not explicitly state that this is a read-only list operation, what response format to expect, or what 'covers' means behaviorally.

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 text is efficient and front-loads the key attribute: plan coverage of connected accounts. It loses a point because it is an incomplete sentence rather than a clear action statement.

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 there are no input ambiguities, and the description gives a broad summary of the expected output. However, it leaves 'the plan' vague and does not explain the output structure, which matters more because no output schema is provided.

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 input schema has zero parameters, so the baseline is 4. The description does not need to explain parameter behavior because there are no parameters to document.

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 identifies the resource as connected social accounts and adds a distinguishing attribute: whether the current plan covers them. This is clearer than a bare restatement of the tool name, though it lacks an explicit verb and does not differentiate against sibling list tools.

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 guidance is given about when to use list_channels as opposed to list_workspaces, list_brains, or list_scheduled_posts. The name implies a listing operation, but the description provides no usage context or exclusion criteria.

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