phone_get_user_call_logs

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

No annotations are provided, so the description carries the full burden. It states the operation (getting call logs) but doesn't disclose pagination behavior (though page_size and next_page_token params imply it), rate limits, permission requirements, or what happens if the date range is invalid. For an unannotated tool, this is a minimal disclosure gap.

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?

Single concise sentence, front-loaded with the action. No wasted words. It's appropriately brief for what it communicates, though it could use the sparse format to add a bit more differentiation value.

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 paginated list tool with 5 params, missing output schema, and no annotations, the description is somewhat thin. Given sibling ambiguity (multiple similar phone call log/history tools), more differentiation would help. However, it's a functionally simple read operation and the required params guide usage. Adequate but could be richer.

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 description coverage is 60% — three params (userId, from, to) are described but page_size and next_page_token have no descriptions in the schema or the tool description. The description doesn't add anything beyond what's already in the schema. With 60% coverage, the description's value-add is limited, though the covered params are clear.

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?

Description is clear: 'Get a specific Zoom Phone user's call logs for a date range' with specific verb+resource+scope. It distinguishes the target user ('specific Zoom Phone user') which helps differentiate it from siblings like phone_get_account_call_logs (account-level) and phone_get_user_call_history. However, it doesn't explicitly contrast with the sibling call_history and call_log detail tools.

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 implies this is for a specific user's call logs within a date range, which signals the main usage context. However, there's no explicit when-to-use vs alternatives, no mention of how it differs from phone_get_user_call_history or phone_get_call_log_details, and the relationship to phone_get_account_call_history is unstated.

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