publish_post

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

Despite no annotations, the description discloses publishing behavior, optional scheduling, media URLs, and return fields (post_id, status, url, error). It does not mention side effects or rate limits, but covers the core behavior sufficiently.

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 structured with a one-line purpose, then a bullet-style Args and Returns section. It is concise and easy to parse, though the Russian language might limit international agents.

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?

Given no output schema, the description includes the return structure. All 5 parameters are explained. It lacks error handling details but is sufficient for correct invocation in most cases.

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 coverage is 0%, but the description provides full parameter semantics: platform options (telegram | youtube | instagram), text, channel, media_urls optional, schedule_at optional with ISO-8601 format. This adds significant value beyond the bare 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?

The description clearly states 'Опубликовать пост на указанной платформе' (Publish a post on the specified platform), specifying the verb and resource. It lists the allowed platforms and distinguishes itself from sibling tools (get_metrics, get_channel_stats) which are read-only.

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 does not explicitly provide when to use this tool versus alternatives. However, the sibling tool names and context imply usage for publishing vs. reading metrics, so it is adequate but not explicit.

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