save_media

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

No annotations provided, so description bears full burden. It only says 'save-to-disk' without disclosing side effects (e.g., overwriting, disk space), permissions, rate limits, or error states. The skipIfExists parameter suggests idempotency, but description does not elaborate.

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?

Three sentences, front-loaded with purpose and usage guidance. No wasted words, though it omits parameter information. Concise but incomplete.

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?

Tool has 6 parameters and no output schema, yet description covers only high-level purpose. Lacks information on return values, error handling, or parameter constraints. Incomplete for the tool's complexity.

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%, yet description adds no parameter details. It does not explain msgId, chatId, folder, filename, timeoutMs, or skipIfExists. Agent cannot infer parameter meaning from description alone.

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 clearly states it's a generic save-to-disk for any media kind (image/audio/video/document). It distinguishes from siblings by naming save_image and save_voice as type-specific alternatives, making the tool's purpose and unique role clear.

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 advises using specific tools (save_image, save_voice) when the type is known for clarity, and recommends this tool for mixed lists of msgIds to avoid branching. Provides clear context and exclusion criteria.

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