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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds one behavioral fact beyond annotations: that no account is needed. This is useful but minimal; it doesn't describe return format or any edge cases, though for a read-only list operation the burden is low.

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 two concise sentences. The core action is front-loaded, and the additional detail about OAuth vs credentials and no-account requirement is placed efficiently without wasted words.

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 parameters, no output schema, and annotations covering safety, the description fully specifies what the tool does and what it returns (list of platforms with connection method). It also clarifies the account requirement, so an agent has all needed information to invoke it correctly.

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 schema coverage is trivially 100%. Per rubric, a baseline of 4 applies when no parameters exist; the description adds no parameter-specific information because none is needed.

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 clear verb ('Lists') and resource ('social platforms PostWire can publish to'), and adds specific detail about the output (whether each connects via OAuth or credentials). This distinguishes it from siblings like list_scheduled_posts, which are clearly about a different resource.

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 explicitly notes 'Does not need a PostWire account,' which signals when this tool is appropriate (e.g., pre-authentication discovery). It does not explicitly list alternatives, but the sibling set is diverse and this tool's purpose is self-evident, so the guidance is sufficient.

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