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

No annotations are provided, so the description carries the full disclosure burden. It does add one genuinely valuable behavior: the webhook secret is never returned, only its set/unset state, plus the 'Owner or office' permission requirement. Otherwise it only restates return fields that the output schema already documents, so it stops short of rich behavioral context.

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 front-loaded sentence that lists the returned configuration and closes with the access constraint; no filler and nothing out of order.

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 one-parameter read with an output schema present, the definition covers purpose, permission scope, and the sensitive-data caveat. It needs only an explicit pointer to phone_setVoiceAi as the mutation path to be fully complete.

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 single parameter shop_id has 0% schema description coverage and is never mentioned in the description beyond the possessive 'the shop's'. The scoping is implied, but no format or requirement details are added, so compensation for the coverage gap is partial.

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 names the specific resource (voice AI configuration) and enumerates its fields (provider, SIP address, webhook-secret flag, provider URLs), so an agent knows this is a read of telephony setup rather than a mutation. It does not explicitly say 'get' or contrast itself with the sibling phone_setVoiceAi, which is the only real gap.

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?

'Owner or office' gives an access precondition but not a when-to-use rule; the agent must infer that this is the inspection counterpart to phone_setVoiceAi. Usage is implied by the content listing rather than stated.

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