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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior — paged retrieval of roughly 100 paragraphs — but then names a parameter 'next_offset' that does not exist in the schema, which weakens the disclosure.

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 short sentences, front-loaded with what the tool returns and followed by the paging rule. No filler, though the second sentence wastes its brevity on an incorrect parameter 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?

An output schema exists, so return values need not be explained. However, with four parameters and half of them undocumented in the schema, the description leaves limit/offset semantics and the 'omit quarter for latest' behavior entirely to the schema, while introducing a phantom parameter name.

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 only 50% (ticker and quarter are documented, limit and offset are not), so the description should compensate. Instead it implies a page size of 100 while the schema allows limit up to 150, and instructs the agent to 'Pass next_offset' — a parameter absent from the schema, where the real field is 'offset'. This actively misleads rather than clarifying.

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 concrete verb and resource ('Get an earnings call transcript') and adds the payload detail of speakers and timestamps. It does not explicitly distinguish itself from the sibling 'search_transcripts', but the retrieval-vs-search framing is implied by 'Get ... transcript'.

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?

There is no when-to-use guidance: nothing tells the agent to prefer this over search_transcripts, or that a quarter key should come from get_company. The only procedural hint is the pagination instruction, which is mechanics rather than tool selection.

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