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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral details about the returned entries: deduplicated platform labels, per-provider handles, a content preview from the first provider, and a dashboardUrl. It does not mention ordering or pagination, but given the read-only annotation and simple scope, this is sufficient.

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 front-loaded with the main purpose, then explains return fields and ends with a practical filtering instruction. Each sentence earns its place, though the enumeration of fields is somewhat detailed.

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 low-complexity, read-only list operation with an output schema, the description covers the scope, key returned fields, and client-side filtering behavior. Nothing an agent needs to invoke it correctly is missing.

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?

There is only one optional 'limit' parameter, and the schema already defines its type, default, minimum, and maximum, making it self-explanatory. The description does not add any param-level meaning or mention pagination, so it provides no value beyond the structured schema.

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 states a specific verb ('List') and resource ('the user's draft posts'), and distinguishes drafts from scheduled posts with '(not yet scheduled)'. This makes the tool's purpose unambiguous and separates it from siblings like list_scheduled_posts without needing to inspect schemas.

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 gives clear context by specifying that this lists drafts, not scheduled posts, and explicitly instructs client-side filtering by platforms/channelNames when a specific platform or account is desired. It does not explicitly name alternatives or edge cases where another tool should be used, so it stops short of a 5.

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