send_invoice

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the mutation/external-effect profile is covered by structured data. The description adds nothing beyond that: it does not mention that sending requires provider_token, that it posts a message into chat_id, or that repeated sends create duplicate invoices despite non-idempotency.

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 single sentence is front-loaded but is drastically undersized for a 31-parameter payment tool. This is under-specification rather than genuine conciseness; the brevity saves nothing because the agent still has to infer the entire contract.

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?

No output schema exists, so the description should explain the return value (a sent Message) and the provider-token prerequisite, and it does neither. For a high-complexity, high-parameter-count payment operation with almost no schema documentation, this definition is far from complete.

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?

With 31 parameters at 13% schema description coverage, the description carries the burden of explaining parameters and does none of it. Critical required fields such as payload, currency, prices and provider_token, plus options like max_tip_amount, need_shipping_address and suggested_post_parameters, are left entirely undocumented.

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 verb and resource are identifiable (send an invoice), but the sentence largely restates the tool name and adds only 'for payment'. It does not say the invoice is delivered as a message into a chat, nor distinguish this from the sibling create_invoice_link, so an agent cannot confidently choose between them from the text alone.

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?

There is no when-to-use guidance, no prerequisite (e.g. a payment provider token must exist), and no mention of the related siblings answer_shipping_query and answer_pre_checkout_query that the invoice flow depends on. Nothing is explicitly misleading, but the agent is given zero routing information.

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