send_media_group

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

Annotations already indicate a non-read-only, non-destructive action. The description adds the 'album' behavior and the 2-10 item count, but does not disclose potential effects, required permissions, or error conditions. This is a modest improvement beyond 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 single, concise sentence that front-loads the main purpose and key constraint. Every word contributes value, with no redundancy.

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 tool's complexity (10 parameters, low schema coverage, no output schema), the description is insufficient. It does not clarify the media array requirements, optional parameters, or expected result, leaving significant gaps for an agent.

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 only 30%, with critical parameters like 'media' left undescribed ('{}'). The description names media types but does not explain the structure of the media array, which is essential for correct invocation. It fails to compensate for the low schema coverage.

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 a specific action: sending multiple media items (photos, videos, documents, audios) as an album, with a 2-10 item constraint. It distinguishes this from single-media send tools like send_photo and send_video.

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 implies when to use the tool: when sending 2-10 media files as an album. However, it does not explicitly state when not to use it or mention alternatives for single media sends, so it falls short of full exclusions guidance.

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