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

Annotations already establish read-only, idempotent, non-destructive, closed-world. The description adds real behavioral context beyond that: tiered plan requirements for different feature classes and the runtime rule that a queue only rings members who are signed in and available. That conditional behavior is not derivable from annotations or schema.

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?

Three sentences, front-loaded with the return contents before the prerequisites and queue behavior. The first sentence is dense but each clause names a distinct component, and no sentence is filler. Slightly list-like, but efficient.

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?

With no output schema, the description carries the burden of describing the return shape, and it does so item by item, plus prerequisites and queue semantics. Missing only explicit scoping versus sibling list tools, which is a minor gap for a zero-arg read tool.

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?

Zero parameters and 100% schema coverage, so there is nothing for the description to clarify; the baseline for a no-param tool is 4. No parameter-related gaps exist.

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 states a concrete read action ("Returns") and enumerates the resource contents precisely: numbers and their answerers, AI receptionists with greeting/knowledge/voice/languages, press-1 menus, queues, and opening hours. An agent can tell what data comes back. It does not, however, distinguish this from siblings like list_pbx or list_did_numbers, which overlap in the phone-system domain.

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?

Usage is only implied — this is the read-all view of phone-system configuration. The description gives plan prerequisites (owner needs Business; queue agents and shared-number users need Business) but never says when to pick this over list_pbx, list_did_numbers, or get_forwarding. No explicit when/when-not routing.

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