zernio_get_whatsapp_phone_number

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. However, it only states 'Get details' without clarifying that this is a read-only operation, what specific details are returned, or any authentication/authorization requirements. The description does not add value beyond the basic action.

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. It is front-loaded with the verb and resource, and contains no extraneous information. Every word earns its place.

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 that there is no output schema and the tool has only two parameters, the description is too minimal. It does not explain what 'details' means, the expected return format, or any side effects. For a retrieval tool, it should provide more context about the result structure or typical usage.

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 already provides clear descriptions for both parameters: 'The phone number ID to retrieve' and 'The WhatsApp Business account ID'. With 100% schema coverage, the description does not need to add extra meaning. Baseline score of 3 is appropriate as the description merely restates the action without parameter semantics.

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 details for a specific WhatsApp Business phone number.' clearly states the verb (Get details) and resource (specific WhatsApp Business phone number). It is specific and unambiguous, but it does not distinguish itself from similar sibling tools like 'zernio_get_whatsapp_contact' or 'zernio_get_whatsapp_business_profile', which also retrieve details for related entities.

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. There is no mention of prerequisites, limitations, or situations where this tool is preferred over other similar tools (e.g., for retrieving a phone number's display name or status). The agent has to infer usage from the tool name alone.

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