send_generic_template

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool sends a message to Instagram chat, but it does not mention authentication requirements, rate limits, delivery semantics, or whether messages are subject to platform messaging windows.

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 front-loaded sentence with no wasted text. It efficiently identifies the action and the card contents, though the parenthetical field list is slightly redundant given the schema.

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?

For a message-sending tool with no annotations and no output schema, the description is under-specified. It explains what is sent but omits operational context such as required permissions, messaging-window restrictions, and failure behavior, leaving an agent without enough information to use it safely.

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 coverage is 100%, so the input schema already documents recipient_id and the nested elements structure. The description only names the visible card fields and does not add syntax or constraints beyond what the schema provides, making the baseline 3 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 states a specific verb and resource: sending a Generic Template carousel card to Instagram chat, and lists the card components. It is clear what the tool does, but it does not explicitly differentiate this from sibling tools like send_button_template or send_quick_replies.

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 guidance on when to use this tool versus alternatives such as send_button_template, send_quick_replies, or send_instagram_dm. The phrase 'carousel card' implies a use case, but the agent must infer the selection criteria.

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