send_quick_replies

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 says the buttons are interactive and tappable in Instagram DMs, but it does not disclose messaging permissions, delivery constraints, rate limits, what happens when a user taps, or how payloads are returned.

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 filler. It efficiently conveys the action, medium, and interactive element.

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?

Although the schema is fully documented, the tool has no annotations and no output schema, and the description does not cover safety, permissions, delivery behavior, or alternatives. For a messaging action in a crowded sibling set, the description is not complete enough to guide correct selection and invocation confidently.

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 100%, and the schema documents recipient_id, message_text, and the quick_replies structure including title length and payload meaning. The description adds no parameter details beyond the schema, so the baseline of 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 states a specific verb and resource: sending a message with interactive Quick Reply buttons in Instagram DMs. It is clear what the tool does, but it does not explicitly distinguish itself from nearby sibling send tools such as send_button_template or send_generic_template.

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 tool is for Quick Reply buttons, but gives no explicit guidance on when to use it versus alternatives like send_instagram_dm, send_button_template, or send_generic_template. With many sibling messaging tools, the missing routing guidance is a real gap.

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