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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: only pending and failed posts are returned, each result carries a workspace label, and the scheduledPostId is the handle cancel_scheduled_post expects — none of which the annotations convey.

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?

Front-loads the core action and scope, then the default-vs-narrow rule, which is the right order. The middle sentence enumerating all seven platforms largely duplicates the provider enum and is the one part that does not fully earn its space.

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 output schema, the description carries the return-value burden and does so adequately by saying results include scheduledPostId values and workspace labels. It stops short of covering ordering, pagination, or result limits for a list tool, which leaves a minor gap for a low-complexity, zero-required-param call.

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 schema already documents both provider and workspaceId including the omit-to-list-all semantics. The description restates the workspaceId default and enumerates platforms that the enum already encodes, so it adds little meaning beyond the schema; 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?

States a specific verb and resource ("List ... scheduled posts") and narrows the scope to pending and failed posts for a workspace, which separates it from list_posts. It also names the downstream consumer of the returned IDs (cancel_scheduled_post), so an agent can place it precisely among siblings.

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?

Gives explicit operating context: default behavior is cross-workspace listing, and workspaceId narrows to one. It implies the follow-up use via cancel_scheduled_post but never states an exclusion such as "use list_posts for already-published posts", so the routing guidance is clear rather than exhaustive.

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