duo_get_telephony_log

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

With no annotations, the description carries the behavioral transparency burden. It adds useful pagination behavior by explaining how to use next_offset with a comma-joined pair from metadata.next_offset. However, it does not mention ordering, output shape, or other behavioral traits an agent might need.

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 two sentences, front-loaded with the core purpose and followed by the key pagination detail. Every sentence earns its place with no redundancy or filler.

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 read-only log tool with all optional parameters, the description covers purpose and pagination mechanics. But with no output schema and no annotations, it could be more complete by mentioning what fields or event data will be returned or how time constraints affect results.

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 100%, so baseline is 3. The description adds real value by clarifying the next_offset format as a comma-joined pair from the previous response's metadata.next_offset, going beyond the schema's generic 'Pagination cursor from a previous response'.

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 clearly identifies a specific verb and resource: 'Get the telephony log (v2)'. It also specifies the content as 'phone call/SMS credit usage events', which differentiates it from sibling log tools like authentication and administrator logs.

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 when to use this tool through 'phone call/SMS credit usage events', but it does not explicitly state alternatives or when not to use it. The sibling tools provide context, but the description itself offers no direct comparison or exclusions.

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