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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds useful scope context (phone and WhatsApp usage) but does not explain upsert semantics—notably whether omitted fields are wiped—which matters given destructiveHint=true. No contradiction with the 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?

A single front-loaded sentence that enumerates the managed fields with no filler. It is efficient, though the terseness leaves the parameter and usage gaps noted above unaddressed.

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 an 8-parameter, destructive, idempotent write tool with no output schema and 13% schema coverage, the description is thin. It omits the required ivr_config_id, ignores is_active, and never clarifies upsert overwrite behavior—all things an agent needs before calling it safely.

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 only 13% (just the timezone IANA note), so the schema does not carry the load. The description maps to several params (business identity→business_name, contact details→email/phone/website, timezone, escalation_instructions), but never mentions is_active or the required ivr_config_id key, leaving two parameters completely undocumented.

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?

States a specific verb pair (creates or edits) and the exact resource: the receptionist's business identity, timezone, contact details, and escalation instructions. This distinguishes it from siblings like upsert_receptionist_knowledge or upsert_receptionist_location. It stops short of naming the nearest sibling (upsert_receptionist), so an agent still has to reason about the overlap.

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 when-to-use guidance, no prerequisites, and no routing among the many upsert/delete receptionist siblings. With tools like upsert_receptionist, upsert_hours, and upsert_queue in the same family, the absence of any disambiguation is a real gap.

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