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

With no annotations, the description carries the full behavioral burden. It does disclose the result content (per-platform publishing mode: cloud vs. desktop app), which is genuinely useful, but it omits whether this is a read-only/safe lookup, whether it requires authorization, or how stale the 'right now' status might be.

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 filler; the two facts an agent needs (which platforms, how they publish) are delivered immediately.

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 one-parameter read tool with no output schema and no annotations, the description adequately explains what comes back. A brief note that it is a safe, read-only lookup before create_post would close the remaining gap.

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 sole parameter documents the workspace name/id and the default-omission behavior, so the schema does the heavy lifting. The description adds nothing about parameters and cannot be expected to, given the schema's completeness.

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 names the specific resource (platforms available to a workspace) and its scope ('can post to right now'), plus the extra dimension of cloud vs. desktop publishing. It is not confusable with any sibling (list_posts, create_post, list_workspaces), though it never explicitly distinguishes itself from them.

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?

'Can post to right now' implies the intended use case of checking availability before creating a post, but the description never states when to call it or what to do if a platform is missing. No alternatives or exclusions are named.

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