send_paid_media

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

Annotations only indicate readOnlyHint=false and destructiveHint=false, and the description adds no extra behavioral context. It does not explain what happens when media is sent (e.g., whether a 'Buy' button appears, if the message is editable, or if any special permissions are required). The description is too minimal to disclose meaningful behavior beyond the tool's name.

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 with no redundancy or filler. It is front-loaded with the key action and resource. Every word contributes meaning.

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?

This tool has 16 parameters, low schema coverage, and no output schema, yet the description provides only the barest idea of its function. It does not explain supported media types, return values, errors, or any edge cases. Given the tool's complexity, the description is severely inadequate for an AI agent to invoke it correctly.

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 38%, and the description does not compensate. Key parameters like 'media' and 'star_count' are undefined in the schema and the description gives no hints about their format or semantics. The only clue is the word 'paid media' which implies stars, but it does not explain how star_count is used.

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 uses a specific verb ('Send') and resource ('paid media') with a clear condition ('requires Stars payment to view'). It clearly distinguishes this tool from the many other send_* siblings, as none of them mention paid media or Star payments.

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 the use case (sending media that must be paid for with Stars) but offers no explicit guidance on when to choose this over alternatives like send_photo or send_invoice. There are no when-not-to-use or exclusion details.

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