get_call_transcript

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

No annotations are present, so the description carries the burden. It discloses the CLAWDCALL_API_KEY requirement, a meaningful credential prerequisite, and 'Fetch' implies a read-only operation. However, it does not describe error cases or return format, leaving some behavior undisclosed.

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 sentences, both essential: the first states the action and identifier types, the second states the required credential. No filler or redundancy, and the key information is front-loaded.

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-parameter read-only fetch tool, the description covers the essential action, the accepted identifier, and the authentication requirement. It does not specify the response shape, but with no output schema, a brief note on what the transcript contains would improve completeness; still, it is largely sufficient.

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 schema already documents the single 'id' parameter with a matching description ('Call ID or campaign ID returned by ClawdCall'), and schema coverage is 100%. The tool description essentially repeats this, adding no new semantic detail, so baseline 3 is appropriate.

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 the specific verb 'Fetch' with the resource 'ClawdCall transcript' and scopes it by 'call ID or campaign ID.' This clearly distinguishes it from sibling tools that send/verify OTPs or place outbound calls.

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 when to use it (when needing a transcript) but does not explicitly contrast with sibling tools or state situations where another tool would be appropriate. The usage context must be inferred from the tool name and sibling set, so it is adequate but not explicit.

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