ghl_voice_ai_get_call_logs

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but no details are given about pagination, data scope, or whether any side effects occur. This is a significant 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?

The description is concise and front-loaded, but it is more under-specified than efficiently structured. A single short phrase does not adequately convey the tool's behavior or usage, making it closer to a bare-bones label than a helpful description.

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?

Given the tool has 4 parameters, no output schema, and no annotations, a 5-word description is insufficient. Missing details such as authentication requirements, pagination behavior, and expected response format leave the agent without necessary context.

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 schema covers agentId and locationId with descriptions, but page and pageSize lack descriptions. The description adds no parameter information at all, so it fails to compensate for undocumented parameters or provide any additional meaning.

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 uses the specific verb 'Get' with the resource 'Voice AI call logs', clearly identifying the operation. It is distinct from sibling tools like ghl_voice_ai_get_agents and ghl_voice_ai_get_agent, though it lacks detail on scope or filtering.

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 guidance is provided on when to use this tool versus alternatives, nor are there any mention of required parameters like locationId and agentId or how to interpret results. The description simply states what it does without usage context.

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