send_carousel

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

With no annotations provided, the description carries full responsibility for disclosing behavior. 'Send Carousel' only implies a send operation and discloses no side effects, requirements (e.g., chatId vs phone), expected output, or error conditions.

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 two words, but this is under-specification rather than conciseness. There is no front-loaded information because there is no information at all; the short length does not help the agent.

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 5 parameters, numerous sibling send tools, no output schema, and no annotations. The description is completely inadequate for an agent to select and invoke this tool correctly; it fails to provide even the most basic contextual information.

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 0%, and the description does not explain any of the 5 parameters (body, phone, chatId, params, quotedMsgId). The agent has no idea what the 'params' array should contain or how it relates to a carousel, so the description adds zero semantic value.

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 'Send Carousel' merely restates the tool name 'send_carousel' with no additional meaning. It does not specify what a carousel is, what action is performed, or how it differs from other send_* siblings like send_list or send_button. This is essentially a tautology.

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 the many sibling send_* tools. The description provides no context, prerequisites, alternatives, or exclusions, leaving the agent with no criteria for selecting this tool.

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