whatsapp_list_newsletters

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states a list operation but does not mention read-only nature, authentication needs, rate limits, or output format. This is insufficient for a tool with no metadata.

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 highly concise with a single phrase. It is front-loaded with the core action and resource. While brief, it lacks any supplementary context but is efficient.

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 zero-parameter schema and no output schema, the description is the sole source of information. It does not explain what the returned list contains (e.g., names, IDs, objects), leaving agents uncertain about how to use results. This is incomplete.

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?

There are no parameters, and the input schema is empty. The description adds no parameter info, but the baseline for 0 parameters is 4. It correctly implies no input is needed.

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 'List all subscribed newsletters' clearly states the verb (list) and resource (subscribed newsletters), distinguishing it from sibling tools like 'whatsapp_get_newsletter' (get single) and 'whatsapp_set_newsletter_subscription' (modify subscription).

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 using 'whatsapp_get_newsletter' for details on a specific newsletter. The simple phrase does not set context or exclusions.

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