list_calls_turn_keys

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

With no annotations, the description must carry the behavioral burden; it only says 'List', which implies a read operation but does not disclose whether the response contains sensitive TURN credentials, whether results are paginated, or any permission requirements. For a tool returning credentials, this lack of context is a meaningful 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 one short sentence with no filler and front-loads the verb and resource. It is appropriately concise for a simple one-parameter list tool, though it could be more informative without becoming bloated.

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 one-required-parameter, no nested objects, no output schema tool, the description provides the essential action and scope, making a correct call plausible. However, the lack of any note about return shape, pagination, or the distinction from get_calls_turn_key leaves the description just barely complete.

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 input schema already documents account_id with 100% coverage, so the description adds no parameter-level meaning. The description correctly implies the account scope by mentioning Cloudflare Calls, but this is not enough to raise above the schema-covered baseline.

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 the exact verb (List), resource (TURN keys), and product scope (Cloudflare Calls), which distinguishes it from sibling tools like get_calls_turn_key (single-key get) and list_calls_apps (Calls apps).

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 verb 'List' implies this tool is for fetching the full collection of TURN keys rather than a single key, but it never explicitly says when to prefer it over get_calls_turn_key or how to handle an account with many keys. No alternatives or exclusions are named, so guidance is only implicit.

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