send_story

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds parameter-level behavior (e.g., period_seconds values, pinned effect) but does not disclose broader consequences like post visibility, rate limits, or the need to have media accessible. No contradiction with annotations.

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 a compact paragraph plus an Args list. It front-loads the purpose and uses bullet-point-style entries for each parameter, with no redundant information.

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 the 6-parameter complexity and zero schema descriptions, the description covers all parameter semantics and the primary action well. It does not mention usage context or edge cases, but an output schema exists so return values are not required. The tool is adequately specified for invocation.

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% and the description provides essential semantics for all 6 parameters, including allowed values for period_seconds (21600/43200/86400/172800), privacy options, and explanation of pinned and noforwards. This fully compensates for the schema's lack of descriptions.

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 'Опубликовать новую story' (publish a new story) and specifies it handles photo/video. This distinguishes it from sibling story tools like get_* or delete_stories.

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?

There is no explicit guidance on when to use this versus alternatives. The purpose is implied by the name and the verb 'publish', but no exclusions or alternative tools are mentioned. It relies on the agent to infer that this is the only tool for creating stories.

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