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

No annotations are provided, so the description carries the full burden, yet beyond implying a read-only lookup it discloses nothing about behavior: no result ordering, no note on partial/fuzzy matching, no device/permission requirements, no paging behavior. The safety profile can only be guessed from the word "search".

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?

Two short sentences with the core capability front-loaded and zero filler. The second sentence ("Same as get_whatsapp_chats with action 'search'") is slightly awkward given get_whatsapp_chats is also a standalone sibling, but it is compact and informative.

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 5-parameter search tool with no annotations and no output schema, the description covers the what but not the how: nothing on paging through large result sets, on whether the device must be linked, or on what a match looks like. It is adequate to call the tool, but thin given the missing structured 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 baseline is 3; the schema already documents query, device, page, limit and contactTypes. The description adds only a slightly richer account of what the query string matches against (company, metadata, private notes) beyond the schema's generic "free text to search for".

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 and resource (search chats by name) and enumerates the searchable fields — contact name, group name, phone number, company, metadata, private notes. This distinguishes it reasonably well from siblings like get_whatsapp_chats_by_status or get_whatsapp_chats_by_date_range, though it never explicitly names a sibling.

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?

"Perfect for quickly finding specific conversations" implies usage, and the note that it equals get_whatsapp_chats with the search action hints at an alternative path. But there is no explicit when-to-use / when-not-to-use guidance against the many adjacent list tools, leaving the agent to infer routing.

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