Get Call Activities And Transcriptions

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower. The description adds real value beyond that: it discloses the response shape (a `plan` with total_pages and batches), the default target_calls of 500, and that transcripts are truncated, giving an agent the behavioral context to plan the fan-out.

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?

Front-loaded with the flow position and the single GET, then layers the response structure and dispatch instruction. Dense but every sentence earns its place; no filler or repetition of the name.

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 nine-parameter, multi-step fan-out tool with no output schema, the description is fairly complete: it explains the returned `plan`, the batch model, and the per-call fields, effectively compensating for the missing output schema. Auth/permission preconditions are the only notable gap.

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 coverage is 100%, so the schema already documents all nine parameters and the baseline is 3. The description reinforces a few params (default target_calls 500, transcript truncation via max_transcript_chars) but adds little syntax or meaning the schema doesn't already carry.

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 and resource: 'one GET against the CTM calls endpoint returning a page of answered calls with transcriptions.' This is precise and an agent can tell it apart from the auth/run-status siblings, though it never explicitly names an alternative tool the way the top-tier examples do.

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?

Frames the tool as 'Step 3 of the review flow' and prescribes the workflow: 'Dispatch one subagent per batch; each subagent calls this tool with that batch's page and per_page.' Clear procedural context, but no when-not-to-use guidance or named alternatives.

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