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

With no annotations, the description carries the behavioral disclosure burden. It discloses the return format (ordered speaker turns with speaker name, role, and section), the ~2 MB text cap, the truncated flag behavior, and how to slice via components=. Text coverage 2020-2025 is also stated. It could add error handling details but covers the key operational behaviors.

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?

The description is three sentences, densely packed with purpose, usage, output structure, limits, and coverage. Every sentence adds new information without fluff, and the key point 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 tool with no output schema and no annotations, the description covers the core purpose, when to use it, how to obtain event_id, the output structure, limits, and error flags. It does not detail max_turns behavior or error scenarios, but the essentials for an agent to invoke it correctly are present.

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 only gives minimal 'Path parameter' descriptions for two required params, leaving max_turns and components without schema explanations. The description compensates by explaining event_id's provenance and components= for slicing, but max_turns remains unexplained. Since 50% schema coverage is weak and the description adds some but not complete parameter context, a 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 opens with 'Full earnings-call transcript as ordered speaker turns' which clearly identifies the tool's function as returning the verbatim transcript. This distinguishes it from sibling transcript tools like list and search, which likely return metadata or search results.

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 phrase 'use when the user wants what management or analysts actually SAID on a call' provides an explicit trigger condition. It also explains where event_id comes from, which guides users to prerequisite endpoints. However, it does not explicitly name alternatives or state when not to use this tool.

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