save_draft

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

Annotations indicate a write operation; description adds that drafts sync across devices and that formatting occurs at send time, going beyond structured data. No contradiction.

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?

Concise purpose sentence followed by a brief args list; every sentence adds value with no redundancy. Well-structured and front-loaded.

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?

Covers core behavior and key parameters; output schema exists for return values. Missing details on remaining parameters are minor, but the tool has 5 params so some context is still lacking.

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?

Adds semantics for text (empty string clears) and parse_mode (client hint), but chat, reply_to, and link_preview remain unexplained. Partially compensates for 0% schema coverage but not fully.

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?

Description states 'Сохранить серверный draft в чате' with sync detail, clearly identifying the resource and action. Distinguishes from sibling tools like clear_draft and get_drafts.

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?

Explains that empty text clears the draft, which implicitly provides an alternative to clear_draft. Also clarifies parse_mode as a client hint for sending, but does not explicitly name alternative tools.

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