whatsapp_get_chat_business_profile

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

With no annotations and a one-line description, the tool offers no insight into behavioral traits like required permissions, error conditions, or whether the chat must belong to a business account. The description carries the full burden but fails to disclose any such information.

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 concise—a single sentence with no superfluous text. It is front-loaded with the purpose, but the brevity may come at the cost of completeness.

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?

Given the simplicity (one parameter, no output schema, no annotations), the description is insufficient. It lacks information about return values, error cases, and prerequisites, making it incomplete for an agent to reliably use the tool.

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?

The schema covers the sole parameter 'chatId' with description 'Chat JID', achieving 100% coverage. The tool description adds no extra meaning about the parameter beyond the schema, so baseline 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 clearly states 'Get business profile for a chat', which specifies the action and resource. It differentiates from siblings like 'whatsapp_get_chat' or 'whatsapp_get_user_profile' by focusing on business profiles, but does not elaborate on what constitutes a business profile.

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?

No guidance is provided on when to use this tool versus alternatives such as 'whatsapp_get_chat' or 'whatsapp_get_user_profile'. There is no mention of prerequisites or scenarios where this tool is appropriate.

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