Get earnings call transcript

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

The description declares 'Read-only,' which aligns with the annotation readOnlyHint=true, but adds little beyond that. It mentions optional filtering by fiscal period or search text, but does not disclose rate limits, auth requirements, or error behavior for missing tickers.

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: the first defines the function and constraints, the second states use cases. No redundant words, tightly packed with relevant 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?

For a tool with 6 parameters (1 required) and no output schema, the description covers purpose, filtering, and use case. It hints at output structure ('speaker-tagged chunks'), but could mention that maxChunks defaults to 80 (available in schema) or that chunks are returned in order.

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 input schema already describes all parameters adequately. The description only summarizes filtering options without adding new semantics or format details beyond what the schema provides.

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 specifies 'Fetch speaker-tagged earnings-call transcript chunks for one exact Bullrun ticker', which is a specific verb-resource pair. It distinguishes from siblings like get_financial_history or get_forward_estimates by focusing on qualitative transcript data, not quantitative metrics.

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 advises using this tool for 'management guidance language, analyst Q&A, and qualitative judgment not visible in financial statements,' providing clear context. It lacks explicit exclusion statements or alternative tool mentions, but the sibling list implies alternatives for quantitative data.

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