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

With no annotations, the description carries the full behavioral burden but only says the tool lists chats. It does not disclose whether it is read-only, whether authentication is required, how results are ordered, whether pagination exists, or what happens with default limits.

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 text is very short, but it is a label rather than a structured description. Its brevity comes from under-specification rather than efficient communication, so it fails to front-load useful context.

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?

For a simple list tool with no output schema, the description still leaves key information missing: parameter behavior, when results are empty, and any read/pagination semantics. It is not complete enough for reliable invocation without inspecting the schema.

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 description coverage for both parameters is 0%, and the description adds no meaning for 'limit' or 'search'. It does not explain filtering syntax, default limits, or what 'search' matches against, leaving the two parameters entirely undocumented.

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?

States a specific verb ('list') and resource ('chats') and adds the platform context ('WhatsApp Web'). It is clear enough to distinguish from siblings by resource, though it does not explicitly name alternatives or differentiate further.

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 when-to-use guidance, no conditions for selecting this tool over alternatives like converse or list_group_participants, and no prerequisites or exclusions. Usage is only implied by the name.

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