vapi_get_call_artifacts

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

No annotations exist, so description carries full burden. It states 'deep diagnostic artifacts' but does not specify types (e.g., audio, logs), or whether it is read-only. Minimal behavioral disclosure beyond requiring a completed call.

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?

Single sentence, front-loaded with key verb and resource. No redundant or unnecessary words. Perfectly concise.

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 zero annotations, no output schema, and many sibling tools, the description is too brief. It does not explain return format, artifact types, error conditions, or pagination. Incomplete for a diagnostic extraction tool.

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 has 0% description coverage for the 'id' parameter. The description adds meaning by implying 'id' is the call ID from a completed call, but does not provide additional constraints or format details. Baseline 3 due to low coverage.

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 specific verb 'Extract' and resource 'deep diagnostic artifacts' with context 'from a completed call'. It clearly distinguishes from siblings like vapi_get_call (basic call info) and vapi_evaluate_call (evaluation).

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 usage after a call is completed, but does not explicitly state when to use vs alternatives like vapi_get_call or vapi_evaluate_call. No exclusions or prerequisites provided.

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