Publish a photo story

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the write/network profile is covered. The description adds real behavioral value by disclosing the three-step server-side workflow (get upload server, upload, save), which explains latency and partial-failure risk. It does not mention retry/duplicate-publication risk, so it is not exhaustive.

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, no filler, with the core action and the multi-step nature front-loaded before the personal/community branch. Every clause 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?

An output schema exists, annotations cover the safety profile, and the schema fully documents parameters, so the description need not restate return values. It is complete enough to invoke correctly, with only the retry/idempotency caveat for a non-idempotent publish left implicit.

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 link_text enum, group_id sign convention and add_to_news default is already documented. The description only restates the personal-vs-community distinction that group_id's own description already carries, adding little 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 and resource ('Publish a photo story on VK') and differentiates itself from the sibling vk_stories_post_video by naming the media type. The parenthetical upload flow further pins down what the tool actually does.

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?

Explicitly states the two modes of use: a personal story by default, or a community story when group_id is set. It gives clear context for the main branching decision but stops short of stating when-not to use it or naming alternatives for related actions.

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