get_crm_customer

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

With no annotations provided, the description carries full transparency burden. It indicates a read operation but does not disclose whether the contact must exist, what happens if the number is not found, or if there are any side effects. Behavioral traits are minimally addressed.

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, efficiently conveying the core purpose. There is no extraneous content. However, it could be restructured to include brief usage notes without sacrificing conciseness.

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 simplicity of the tool (single required parameter, no output schema), the description provides adequate context for a basic lookup. However, it omits what data is returned (e.g., which contact fields), which would help an agent understand the output. With no output schema, this is a notable gap.

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 coverage is 100% (the sole parameter 'whatsapp_number' is described). The description adds context that the number is WhatsApp and ties to internal CRM, but this largely echoes the schema's description. It does not provide additional details like format, validation, or expected input constraints beyond the schema.

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 'Obtiene los datos de un contacto del CRM interno' (gets data of a contact from internal CRM) and specifies the query method 'por su numero de WhatsApp'. This distinguishes it as a lookup tool for internal CRM contacts by WhatsApp number, though it does not explicitly differentiate from siblings like 'get_customer_info'.

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?

There is no guidance on when to use this tool versus alternatives such as 'search_customers' or 'get_customer_info'. The description does not mention prerequisites, limitations, or scenarios where this tool is preferred.

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