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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description adds useful context: it returns newest-first by default, includes AI summary and sentiment only when Rinkel AI insights are available, and maps to GET /call-detail-records. It does not cover pagination behavior or authentication requirements, but those are less critical for a read-only list tool.

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 front-loaded with the core purpose, followed by concrete usage examples, default ordering, and the API endpoint. It is appropriately sized for a 24-parameter list tool and no sentence feels redundant.

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 complex list tool with 24 optional filters and no output schema, the description does enough: it names the returned fields, clarifies default ordering and AI-insight conditions, and provides realistic query examples. The schema covers parameter details, though the description could have mentioned pagination or explicitly routed voicemail-specific queries to rinkel_list_voicemails.

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 the input schema already documents all 24 parameters in detail. The description reinforces the kinds of data available and implies filterable dimensions such as date, direction, status, duration, and users, but it does not add syntax or constraints beyond what the schema provides.

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 specific verb and resource: it lists call detail records, both inbound and outbound, and enumerates the fields returned. It is clearly distinguishable from a single-call getter, but it does not explicitly differentiate itself from adjacent list tools such as rinkel_list_voicemails or rinkel_list_recordings.

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?

It gives concrete use cases such as 'who called today', 'which calls did we miss this week', and 'calls longer than 5 minutes', which clearly indicate when to use the tool. It does not state when not to use it or name alternative sibling tools for related queries.

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