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

The annotations already declare this as a safe, idempotent read operation. The description adds the domain context that these are contact options for a free diagnostic call, and does not contradict any annotations.

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?

One compact sentence conveys the full resource list and the optional-parameter behavior. There is no wasted text and the key information is front-loaded.

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 single-optional-parameter read-only tool, the description fully covers what the agent needs: what data will be returned and how to control it. No output schema is needed because the return content is explicitly enumerated.

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 schema already documents the channel parameter with 100% coverage, providing a baseline of 3. The description adds meaningful guidance by explaining that omitting the parameter returns all channels, enriching 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 what the tool returns—email, phone, WhatsApp, and a booking link—using a specific resource. It is immediately distinguishable from siblings like get_pricing and list_posts by its focus on contact channels.

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 phrase 'Omit channel to get all' provides concrete usage guidance for the optional parameter. It does not explicitly name alternatives or exclusions, but the domain is clear enough that an agent knows when to call this tool.

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