kopern_connect_whatsapp

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

Annotations indicate idempotentHint=true and readOnlyHint=false. The description adds the requirement of Meta Cloud API credentials, but it does not disclose other behavioral traits such as side effects, conflict behavior if already connected, or error scenarios. The description provides some added context but insufficient for high transparency.

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 (one sentence) but lacks structure (no bullet points, sections). It is not overly verbose, but brevity sacrifices coverage of important details for a connection tool.

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 there is no output schema and the tool has 5 parameters, the description is too minimal. It omits expected outcomes, error handling, or how to obtain credentials. The lack of output format information leaves the agent with incomplete context.

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%, so the schema fully documents parameters. The description mentions credentials but does not add extra semantic meaning beyond the schema descriptions. Baseline score 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 clearly states the tool's action: 'Connect an agent to WhatsApp Business'. It specifies a prerequisite ('Requires Meta Cloud API credentials') and distinguishes from sibling tools (e.g., connect_slack, connect_telegram) by naming the specific service.

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 gives a usage hint by mentioning required credentials, but it does not explicitly state when to use this tool over alternatives or provide exclusions. Among sibling connect tools, there is no guidance on selection criteria.

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