whatsapp_get_user_profile

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

No annotations are provided, so the description alone must disclose behavioral traits. It only states 'Get profile info', which suggests a read operation, but does not mention any requirements (e.g., user must exist) or potential side effects. Annotations would help, but they are absent.

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 a single concise sentence that directly states the tool's purpose without unnecessary words or repetition.

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?

Despite having no output schema, no nested objects, and only one parameter, the description is adequate for a simple lookup tool. However, it lacks details on what fields 'profile info' includes, and does not explain behavior if phone is not found or if the user is not a contact.

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 input schema has one parameter (phone) with 100% schema description coverage. The description does not add meaning beyond the schema's 'Phone number (e.g. 1234567890)'. Baseline of 3 applies since schema already documents the parameter adequately.

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 description clearly states 'Get profile info for a specific user by phone number', which includes a specific verb, resource, and context. It distinguishes from sibling tools like whatsapp_get_contact or whatsapp_get_chat_business_profile.

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 implies the tool is for fetching a user's profile via phone number, but does not explicitly state when to use it versus alternatives like whatsapp_check_user or whatsapp_get_contact. No exclusions or prerequisites are provided.

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