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

With no annotations, the description carries the full burden. It does disclose useful behavior: per-target caption fallback, post-type defaulting to reel, and the ignore-priority of single-target fields. It says nothing about what publishing does irreversibly, permission/auth requirements, partial-failure behavior when fanning out to many accounts, or rate limits — significant gaps for a high-stakes write action.

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?

Three sentences, zero filler, front-loaded with the primary action followed by the two calling shapes and the scheduling flag. Each sentence earns its place.

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 9-parameter mutation tool with no annotations and no output schema, the description covers parameter interplay well but omits the return value (per-target success/failure or post ids) and error behavior. An agent would still be guessing about what comes back after a multi-account publish.

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 the schema already documents every parameter, including the publish_targets sub-fields and their captions. The description mostly restates the same mutual-exclusion and defaulting rules rather than adding syntax, format, or constraint details the schema lacks. 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?

The description opens with a specific verb+resource+scope: 'Publish or schedule an asset to one or many connected social accounts.' That is far more informative than the name alone. It does not explicitly contrast with near-neighbor siblings such as schedule_calendar_row or schedule_all_calendar_rows, so an agent must infer the asset-vs-calendar-row boundary.

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?

It clearly states the two invocation modes — multi-account via publish_targets, single via publish_platform + publish_account_id — and that an empty publish_scheduled_at means publish now. That is genuine when-to-use guidance. It gives no exclusion rules against sibling scheduling tools, which keeps it below a 5.

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