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

With no annotations, the description carries the full burden, and it does real work: it discloses that the response includes transcripts, recordings, cost, carrier cost, and conditional fields like refusal (only for SAGOT-refused calls) and disclosure (whether the person was told it is AI and recorded). It omits auth/scope requirements and what happens for an unknown or cross-workspace id, keeping 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?

Front-loaded with the core purpose, then dense field documentation with no filler sentences. The nested brace-expansion notation for disclosure and runtimeStartup makes it denser than ideal to parse, but every clause carries information.

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?

There is no output schema, so the description must explain the return values, and it does cover the non-obvious ones (refusal, disclosure, runtimeStartup) with their sub-fields. Parameter documentation and error/permission behavior are the remaining gaps for a two-required-param read 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 description coverage is 0% and both parameters (id, workspaceId) are bare UUID-typed properties, yet the description never mentions either. The names and UUID patterns make the intent largely inferable, but the description adds no meaning about which workspace scope or id form is expected, so it fails to compensate for the coverage gap.

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?

Opens with a specific verb and scope, 'Read one call', and enumerates the payload (status, outcome, transcript, recording, cost, carrier cost), which clearly separates it from sibling calls_list and calls_recording. It never explicitly frames the single-vs-list distinction as guidance, only referencing calls.list for refusal semantics, so it stops short of a 5.

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?

Usage is only implied: the tool takes an id, so the agent infers 'use after calls_list returns an id', but that is never stated. No guidance on when to prefer calls_recording or the state-mutating siblings (calls_cancel, calls_approve, calls_decline), and no exclusions are given.

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