publish_post_now

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'immediately' and 'auto_adapt threading' but fails to explain side effects, permissions, rate limits, return values, or what auto_adapt threading actually does. The mutation nature is implicit but vague.

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, tightly worded sentence with no filler. The parenthetical adds a useful feature note. Every word 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 tool with 6 parameters, a nested networks object, and no output schema, the description is severely under-specified. It does not explain required fields, return values, or the structure of nested objects, leaving the agent guessing.

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 0%, so the description must compensate for parameter meanings. It only hints at auto_adapt threading, which likely maps to the auto_adapt parameter, but leaves the other five parameters (text, networks, media_ids, account_ids, follow_up_text) without any semantic explanation.

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 'Publish a post immediately' – a specific verb and resource. It clearly distinguishes from scheduling tools like schedule_post by emphasizing 'immediately'. However, it does not explicitly distinguish from publish_with_media or other immediate publishing variants.

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 provides no guidance on when to use this tool versus alternatives like schedule_post or publish_with_media. There are no exclusions, prerequisites, or contextual hints for selection.

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