resolve_email_contact

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

No annotations are provided, so the description must carry the full burden. It states the tool 'searches for the email' using CRM and e-commerce, implying a read-only operation, but it does not explicitly disclose whether the tool modifies data, what happens if no email is found, or any other behavioral traits. The description lacks sufficient detail.

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 in Spanish. It includes the core purpose. It is front-loaded but could benefit from being slightly more structured (e.g., listing CRM and e-commerce as data sources). 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 tool has only one parameter and no output schema or annotations, the description is minimally adequate. It explains what the tool does but does not cover return format, error handling, or usage context. It is complete enough for a simple lookup but lacks richer 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?

The input schema has 100% coverage (one parameter with description). The tool description adds no extra meaning beyond the schema's description of 'phone_hash'. Baseline score of 3 is appropriate.

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 the tool's purpose: resolving an email contact by searching for the email associated with a WhatsApp contact using CRM and e-commerce platforms. The verb 'resolve' is specific, and the resource (email contact) is distinct from siblings like 'search_email_contacts' or 'get_crm_customer'.

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or when not to use it. With many sibling tools, such guidance is essential.

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