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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the agent knows this is an irreversible public write. The description adds only capability scope, not the behavioral context an agent would want at call time, such as confirmation requirements, failure/partial-publish behavior, or the fact that publishing is public and cannot be undone.

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?

Two sentences, front-loaded with the core verb and resource, followed by a compact feature enumeration. No filler or restatement of structured data.

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 an 11-parameter tool with nested platform objects and no output schema, the description is thin: it omits idempotency/dry-run semantics, mutual exclusions (schedule vs queue_id), and any sense of return value. The schema compensates for much of this, but the description itself does not.

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 description coverage is 100%, so every parameter, including the rich nested 'platforms' object, is already documented. The description only names the 'platforms' parameter and repeats the X/Threads thread limitation, adding essentially no meaning beyond the 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?

States a specific verb+resource ('Publish a post to specified social media profiles') and enumerates the supported capabilities. It does not, however, differentiate itself from sibling post_publish_draft, which is left for the agent to infer from the name alone.

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 lists what the tool supports but gives no when-to-use guidance: no indication of when to prefer this over post_publish_draft, post_update, or a queue-based flow, and no mention of prerequisites such as connected profiles or required placements.

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