whatsapp_get_messages_by_contact_name

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

No annotations provided; description is too brief. Lacks disclosure of return format, ordering, pagination, error handling (e.g., contact not found), or whether messages are marked as read. Important behavioral traits missing.

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 sentences, front-loaded with purpose. No wasted words, but could be slightly more informative without losing conciseness.

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?

With many sibling tools and no output schema shown (though context says it exists), the description is adequate for simple usage but lacks completeness for confident tool selection. Missing context on when to use this over similar message-retrieval tools.

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?

Adds meaning beyond schema: explains only_today as 'filter today only' and limit with default 20. Name parameter is clear from context. Schema coverage is 0%, so description compensates well for 2 of 3 parameters.

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?

Clearly states 'Get messages from a contact by name/nickname', specifying the verb and resource. Implicitly differentiates from siblings like whatsapp_get_messages (by chat ID) and whatsapp_search_messages (more extensive), but lacks explicit differentiation.

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?

Implies usage when contact name is known, but no explicit guidance on when to use vs alternatives like whatsapp_get_messages or whatsapp_get_unread_messages. No when-not or alternative recommendations.

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