whatsapp_get_messages

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

Only discloses that messages are sorted by timestamp. With no annotations, the description carries full burden, but it fails to mention read-only nature, authentication needs, or error handling (e.g., invalid phone). Minimal behavioral context.

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?

Short and front-loaded with key info: one sentence plus two parameter hints. No fluff, but could benefit from slight restructuring (e.g., separate parameter details).

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?

Adequate for a simple 2-parameter tool, but missing context like what 'recent' means (time range), pagination, and error behavior. Output schema exists but description doesn't reference return format. Gaps remain given no annotations.

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 to 'phone' (format constraint: no '+') and restates default for 'count' (already in schema). With 0% schema description coverage, this is helpful but incomplete—does not explain that phone identifies the chat or what count limits.

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?

Description clearly states it gets recent messages from a chat, sorted by timestamp, using phone as identifier. Distinguishes from siblings like get_messages_by_contact_name and get_unread_messages by focusing on a specific chat via phone number.

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?

Provides formatting hint for phone (no '+') and notes default count, but does not specify when to use this over similar tools like get_unread_messages or search_messages. No exclusion criteria or alternative recommendations.

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