List live calls

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

The annotation readOnlyHint=true already declares the safe-read profile, and the description's 'Read-only' merely repeats it. It does add genuine context by narrowing the return to UUIDs only ('currently in progress', 'still queued'), but says nothing about permissions, result size, or freshness. Adequate against an already-covered safety profile.

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?

Two short sentences, no waste, and the core scope ('calls currently in progress') is front-loaded before the optional queued behavior and the sibling pointer.

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?

With no output schema, the description correctly specifies the return payload (UUIDs), and annotations carry the safety profile, so an agent has enough to call it. Minor gap: no guidance on whether subaccount calls are included or how fresh the in-progress list is.

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% and the single boolean is fully documented in the schema, so baseline is 3. The phrase 'optionally calls still queued' restates the parameter's meaning without adding format, default, or interaction detail beyond the schema.

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?

States a specific verb (list) and resource (calls currently in progress) plus the exact payload returned (UUIDs), and explicitly scopes to 'this account'. It also names the sibling (get_call_status) it is distinct from, so an agent can separate the two without opening either schema.

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?

Routes the agent to get_call_status when it needs details of a single call, which is exactly the alternative an agent would otherwise confuse this with. It does not mention list_call_records as the alternative for completed/historical calls, so the when-not coverage is incomplete.

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