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

Annotations already disclose the safe, read-only, idempotent nature. The description adds behavioral context by positioning this as the first call in the workflow and explaining handling of the WhatsApp URL. It does not contradict any annotation.

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 only two sentences, front-loaded with the core fact list, then a clear usage directive and conditional action. Each sentence contributes value with no redundancy.

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?

For a zero-parameter, read-only lookup, the description sufficiently explains what facts are returned and the follow-up action for human contact. Given the simple scope and strong annotations, no essential information is missing.

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 tool has zero parameters, so the schema provides complete coverage. The description adds no parameter details, but none are required; the baseline for 0 parameters is 4.

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 identifies the tool as providing company facts for Jenesis Travel, listing specific content (licence, contact, WhatsApp, enquiry-led model). This specific verb+resource pairing distinguishes it from sibling tools like get_journey and list_faqs.

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?

It explicitly instructs 'Call this first,' establishing when to use the tool relative to other actions. It also gives a conditional directive ('If the user wants a real person, share the WhatsApp URL'), providing actionable guidance beyond the basic purpose.

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