publer_publish_post_now

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

The description states that the tool returns a job_id, hinting at asynchronous behavior. With no annotations provided, the description carries full burden; however, it does not disclose potential side effects, authentication requirements, or error states. Adequate but not thorough.

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 sentences with no wasted words. It front-loads the core purpose and outcome, making it easy to parse.

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?

The description lacks details on parameter relationships (e.g., required conditions for different content types) and does not explain the async workflow fully. With no output schema, more context on return value would help. Adequate but incomplete.

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 input schema already documents each parameter. The description adds no additional semantic detail beyond 'across selected accounts' which maps to account_ids. Baseline 3.

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 clearly states the action (publish immediately) and the resource (post across selected accounts). It specifies the outcome (returns a job_id). However, it does not differentiate from sibling tools like publer_create_post, which likely handles scheduled posts.

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 word 'immediately' implies use for instant publishing, but there is no explicit guidance on when to use this tool versus alternatives like publer_create_post or publer_update_post. No exclusion criteria or prerequisites are mentioned.

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