wa_phone_retrieve_profile

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states 'retrieve' implying a read-only operation, but doesn't clarify authentication needs, rate limits, error conditions, or what the profile contains. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, clear sentence with zero wasted words. It's appropriately sized for a simple retrieval operation and front-loads the essential action and target.

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 no annotations, 0% schema coverage, no output schema, and multiple similar sibling tools, the description is incomplete. It doesn't explain what a 'phone number profile' entails, how it differs from other phone-related retrievals, or what to expect in return. More context is needed for effective tool use.

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 0%, so parameters 'wabaId' and 'phoneNumber' are completely undocumented in the schema. The description adds no meaning about what these parameters represent, their formats, or examples. It fails to compensate for the schema's lack of documentation.

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 'Retrieve a phone number profile' clearly states the action (retrieve) and target (phone number profile), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'wa_phone_retrieve' or 'wa_phone_retrieve_commerce_settings', leaving ambiguity about what specific profile information is retrieved versus those other retrieval tools.

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 no guidance on when to use this tool versus alternatives. With siblings like 'wa_phone_retrieve' and 'wa_phone_retrieve_commerce_settings', there's no indication whether this tool retrieves different profile data, is for specific contexts, or has prerequisites. The agent must infer usage from tool names alone.

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