save_media_window

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

With no annotations, the description fully discloses behavior: concurrency, per-item success/failure, abort conditions only on disk_full/disconnect, default folder, error reporting structure. This is comprehensive and leaves no ambiguity about tool behavior.

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 single, dense paragraph with no wasted words. Each sentence adds value: purpose, behavior, failure handling, folder path, abort conditions. Front-loaded with main action.

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 10 parameters, no annotations, and no output schema, the description is remarkably complete. It explains the return format (items[], errors array, ok status), default folder, concurrency, and error handling. Only minor details like per-parameter defaults are left to the schema.

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 50%. The description adds context (e.g., 'bounded concurrency (default 3)', 'per-item results') but does not fully compensate for undocumented parameters like excludeGroups and hours. Baseline 3 is appropriate.

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 starts with a clear verb and resource: 'Bulk-save WhatsApp media from the last N hours to disk.' It distinguishes from sibling tools like save_image or save_voice by specifying bulk and time-window operation.

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 provides behavioral details but does not explicitly state when to use this tool versus alternatives like save_image or list_media_window. Usage context is implied but not directly contrasted with siblings.

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