waha_get_contact

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read-only operation ('Get info'), but doesn't disclose authentication requirements, rate limits, error conditions, or what 'info' includes (e.g., name, phone number, presence). The agent must infer behavior from the tool name and schema alone.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose ('Get info about a specific contact'), making it easy to parse quickly. No structural issues or redundancy are present.

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 and no output schema, the description is incomplete for a tool that retrieves contact information. It doesn't explain what 'info' includes, potential response formats, or error handling. For a read operation in a WhatsApp API context, more detail on data returned and usage constraints would be helpful.

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 100%, with both parameters clearly documented in the schema. The description adds no additional meaning beyond the schema's details for 'contactId' and 'session'. Baseline score of 3 is appropriate since the schema adequately covers parameter semantics without description enhancement.

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 action ('Get info') and target ('about a specific contact'), which is a specific verb+resource combination. It distinguishes from sibling 'waha_get_contacts' (plural) by specifying 'specific contact', but doesn't explicitly contrast with other contact-related tools like 'waha_block_contact' or 'waha_get_profile_picture'.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing a valid contact ID), contrast with 'waha_get_contacts' for listing multiple contacts, or specify use cases like retrieving contact details for messaging or verification.

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