whatsapp_get_my_profile

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

No annotations are provided, so the description carries the full burden. It states 'Get', implying a read-only operation, but does not disclose any behavioral traits such as authentication requirements, rate limits, or what exactly the profile info contains. For a simple retrieval, this is minimally adequate but lacks depth.

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 sentence of five words, conveying the tool's purpose without any extraneous information. Every word is necessary and contributes to clarity.

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 tool has no parameters and no output schema, and the operation is a simple read, the description is complete. It tells the agent exactly what the tool does, leaving no ambiguity.

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 no parameters, so schema coverage is 100% trivially. The description adds meaning by specifying 'own WhatsApp profile info', indicating what the output represents. According to guidelines, 0 parameters baseline is 4, and the description provides sufficient context.

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 'Get own WhatsApp profile info' uses a specific verb ('Get') and resource ('own WhatsApp profile info'), clearly distinguishing it from sibling tools like 'whatsapp_get_user_profile' which would retrieve another user's 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 usage for retrieving one's own profile, but lacks explicit guidance on when to use this versus alternatives like 'whatsapp_get_contact' or 'whatsapp_get_chat'. The context is clear, but no exclusions or alternative mentions are provided.

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