earnings_transcript

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Get' and stops there—no mention of return format, pagination, authorization needs, or whether the operation is read-only. For a retrieval tool, this is a significant gap.

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 a single, efficient sentence that front-loads the core purpose and parameters. There is no wasted word or redundant detail.

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 simple tool with 3 parameters and no output schema, the description gives the essential retrieval request. However, it lacks any detail about the transcript's content or format, and it doesn't distinguish from earnings_transcript_sentiment, which is a closely related sibling.

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 100%, with each parameter described (ticker, year, quarter). The description merely repeats these names without adding extra meaning (e.g., formats, constraints, dependencies). Baseline 3 is appropriate since the schema already covers the parameters.

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 states a specific verb ('Get') and resource ('earnings call transcript') with the key parameters (ticker, year, quarter). It is clear what the tool does and distinguishes from siblings like earnings_history or earnings_transcript_sentiment, though it doesn't explicitly clarify that it returns the raw transcript text.

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?

No guidance is provided on when to use this tool versus alternatives such as earnings_report or earnings_transcript_sentiment. There are no mention of prerequisites, use cases, or exclusions, leaving the agent to infer its suitability from the name alone.

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