Get Contact Detail (person or group)

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

Annotations indicate readOnly and safe behavior. The description adds behavioral specifics: return shape depends on kind (person vs group) and lists included fields. Does not contradict annotations.

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 extremely concise with a clear structure: a one-line summary, bullet-style return details, and an args section. No wasted words.

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 simple single-parameter tool and lack of output schema, the description fully covers what the tool does, return shapes, and how to find the input. No missing 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 coverage is 100% with a description for contactId. The description enriches this by showing example formats and referencing a sibling tool to look up the ID, adding context beyond the schema pattern.

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 title and description clearly state the tool retrieves details for a single contact (person or group) by stable id. It distinguishes itself from siblings like 'whatsapp_list_contacts' by specifying it returns detailed info for one contact.

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?

The description provides guidance on how to obtain the contactId via 'whatsapp_list_contacts' and gives format examples. It implies usage for getting detail after listing, but does not explicitly state when not to use (e.g., for listing multiple contacts).

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