conduyt_get_call

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

No annotations exist, so the description carries the full burden — and it does credibly: declares read-only, names the required permission (dialer:view), and discloses that recording/voicemail URLs are withheld with hasRecording/hasVoicemail flags as indicators. It omits failure/not-found behavior and any rate-limit or pagination context, which keeps it below a 5.

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?

Three compact sentences, zero filler: identity, returned fields, data-withholding caveat, then the permission gate. The scoping information is front-loaded and every clause carries distinct signal.

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 and no annotations, the description steps in to describe return content and safety-relevant behavior, which is exactly what's needed for a single-record read. The remaining gap is error/not-found semantics and confirmation of whether a missing UUID returns null vs. throws.

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?

One parameter at 100% schema description coverage, so the schema already documents "Call UUID." The description echoes the UUID identifier but adds no format, validation, or lookup-fallback details beyond the schema. Baseline 3 applies.

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?

Specific verb+resource ("Get a single call record by UUID") followed by an enumeration of the returned fields and the key data-withholding behavior. An agent can distinguish this from conduyt_list_calls purely from "single ... by UUID" 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?

The "single call record by UUID" phrasing implicitly routes to conduyt_list_calls for browsing/enumeration, and "Requires dialer:view" states the prerequisite. There is no explicit naming of an alternative or a when-not-to-use clause, so it stops short of a 5.

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