phone_get_user_call_handling_settings

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

No annotations are provided, so the description carries the burden. It does disclose the required OAuth scopes (phone:read:call_handling_setting or ...:admin), which is useful behavioral context. However, it doesn't disclose what the return format looks like, whether settings may be absent/defaulted, or behavior when no settings exist. No readOnlyHint means the agent can't infer safety profile from 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?

Two sentences, efficient and front-loaded with the purpose. The scope note adds necessary auth context. Could be slightly more economical but there's zero waste in the text.

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-parameter read tool with no output schema, this is decent but not complete. The scope info is valuable. However, without annotations and without describing the return value shape or error/empty behaviors, it leaves the agent guessing about what it will actually receive. Adequate but with room to improve on output expectations.

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 100% — the userId parameter is described as 'Zoom user ID or email' in the schema. The description adds no additional parameter detail beyond what the schema already provides. Baseline 3 is appropriate since the schema fully documents the single parameter.

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?

Clear verb+resource: 'Get call handling settings' for a Zoom Phone user. The description specifies what's included (business hours / closed hours / holiday routing) and includes the scoping note about required OAuth scopes. Distinguished from sibling read tools like phone_get_user_call_logs by targeting call handling settings specifically.

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 description states what data is returned but doesn't explicitly say when to use this tool vs alternatives. The scope note implies it's for reading (not updating) settings, which distinguishes it from phone_update_user_call_handling_setting, but the guidance is implicit rather than explicit. No exclusions or when-not-to-use guidance provided.

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